<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: roykeano941-eng</title>
    <description>The latest articles on DEV Community by roykeano941-eng (@roykeano941eng).</description>
    <link>https://dev.to/roykeano941eng</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3899209%2F74fa7f8a-6cf9-4b89-a02f-ba071a43bf62.png</url>
      <title>DEV Community: roykeano941-eng</title>
      <link>https://dev.to/roykeano941eng</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/roykeano941eng"/>
    <language>en</language>
    <item>
      <title>Building an MCP-Enabled Sports Data API: Making Sports Intelligence Agent-Discoverable</title>
      <dc:creator>roykeano941-eng</dc:creator>
      <pubDate>Sun, 26 Apr 2026 18:34:11 +0000</pubDate>
      <link>https://dev.to/roykeano941eng/building-an-mcp-enabled-sports-data-api-making-sports-intelligence-agent-discoverable-582d</link>
      <guid>https://dev.to/roykeano941eng/building-an-mcp-enabled-sports-data-api-making-sports-intelligence-agent-discoverable-582d</guid>
      <description>&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;AI agents are getting good at business intelligence tasks. But they still can't access most domain-specific data — it's locked in PDFs, behind paywalls, or formatted for humans.&lt;/p&gt;

&lt;p&gt;I built a sports sponsorship intelligence API that's natively accessible to AI agents via Model Context Protocol (MCP).&lt;/p&gt;

&lt;h2&gt;
  
  
  What It Does
&lt;/h2&gt;

&lt;p&gt;Query: &lt;code&gt;GET /api/match-score?club=everton&amp;amp;brand=Revolut&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Response: Structured JSON with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Match score (1-100)&lt;/li&gt;
&lt;li&gt;Reasoning&lt;/li&gt;
&lt;li&gt;Comparable deals&lt;/li&gt;
&lt;li&gt;Risk factors&lt;/li&gt;
&lt;li&gt;Suggested deal terms&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why MCP?
&lt;/h2&gt;

&lt;p&gt;MCP lets AI agents discover and use your API without custom integration. Any MCP-compatible agent finds the endpoint at:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://sportsignal.agency/.well-known/mcp.json&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Business Case
&lt;/h2&gt;

&lt;p&gt;£83.9M in Premier League sponsorship revenue is changing hands due to the UK gambling ad ban. 11 clubs need new sponsors. I built the scoring layer for this market.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scoring Algorithm
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Fan base reach: 30%&lt;/li&gt;
&lt;li&gt;Digital presence: 20%&lt;/li&gt;
&lt;li&gt;Category fit: 35%&lt;/li&gt;
&lt;li&gt;Sponsorship gap urgency: 15%&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try It
&lt;/h2&gt;

&lt;p&gt;Free tier: all 11 gambling-affected PL clubs → &lt;a href="https://sportsignal.agency/match-score" rel="noopener noreferrer"&gt;sportsignal.agency/match-score&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback welcome — especially on MCP implementation patterns.&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>api</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
