
Sprtx Mcp
net.sprtxPublished by sprtx.netOfficial publisherv1.0.0Updated Oct 24, 2026
Agent-native sports token network. 1,435 tokens across 98 sports, 9 global regions.
Overview
A remote MCP server for browsing the SPRTX sports token registry, letting an assistant search tokens, inspect hierarchy and pricing, and check network stats.
- What you can do
- Search and read tokens by keyword, type, sport, price range or parent, with full detail and hierarchy trees (ancestors and children). Retrieve current price, market cap and volume data for a token. Read demand signals such as waitlist signups and endorsements. Read network summaries, phase indicator, sports categories, organizations and venues. Start a PHER key acquisition request for trading access.
- When to use it
- Useful when someone wants an assistant to explore or compare sports tokens in the SPRTX registry, check pricing and demand signals, or follow the network's growth phase. Browsing is free and needs no account, so it suits exploratory research rather than actual trading.
- Requirements
- A remote Streamable HTTP endpoint; no local runtime, SDK or package is needed. Read-only browsing tools require no authentication. Trading tools are not yet available and would require a paid PHER key.
Installation
In SourceWeft
- Open Sprtx Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/net.sprtx%2Fsprtx-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"sprtx": {
"type": "http",
"url": "https://mcp.sprtx.net/"
}
}
}README
SPRTX MCP Server
Model Context Protocol server for the SPRTX Network, sports tokenization and new global sports economy. Pure PHP. Zero dependencies. Streamable HTTP transport.
1,435 tokens · 98 sports · 9 global regions · $127.74M market cap · GENESIS phase · Updating Weekly
What is this?
An MCP server that lets AI agents discover, browse, and trade structured sports tokens on the SPRTX network. Agents connect via JSON-RPC 2.0 over Streamable HTTP — no SDK, no browser, no UI. Protocol-native access to the entire sports token registry.
SPRTX tokenizes the global sports hierarchy: federations → leagues → teams → athletes → venues. Every asset has a price, a position in the hierarchy, and demand signal. The MCP server is the agent-native entry point.
Connect
Auto-discovery:
Capabilities
Resources (read-only, no auth)
Tools
Trading tools (buy, sell, transfer) require an active PHER key. Coming in v1.1.
Prompts
Quick Start
Initialize a session:
Use the returned Mcp-Session-Id header for subsequent requests:
Architecture
Pure PHP. No Node. No npm. No SDK. Single endpoint, Streamable HTTP transport, session management via filesystem. Runs on any shared hosting with PHP 7.2+.
Token Hierarchy
98 sports. 580 teams. 298 venues. 249 geolocations. 112 leagues. Loading ongoing.
PHER Keys
Agents browse for free. Trading requires a PHER key ($55) — a hardware-backed cryptographic identity on the SPRTX network. PHER (Permissible Human Entry Request) is the authentication layer for the Internet of Sports Protocol.
Agent-native key provisioning is active. First movers acquire positions before public trading opens.
Network Phase
SPRTX is in GENESIS — token registry live, zero transactions on-chain. Phase auto-progresses:
Loading Status
SPRTX is tokenizing the entire global sports economy — 98 sports across 9 global regions and all stakeholders. Token hierarchies (federations and leagues, teams, athletes, venues) are loading continuously as the network expands. New assets come on-chain weekly.
Agents should poll get_network_stats periodically to track growth.
Early-connected agents see new assets first and can benefit most.
Protocol
Built on the Internet of Sports Protocol (IoSP) — an open protocol for sports data sovereignty. IoSP spec is CC BY-SA 4.0. This MCP server is Apache 2.0.
Naming Conventions
License
Apache 2.0 — see LICENSE.
Copyright 2026 SPRTX INC
Source: README.md at commit 999f338
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts