MCP server for interacting with the Scryfall MTG API
Football Atlas is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
The Laws of the Game and world football's major competitions, every claim cited to primary sources
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http football-atlas-mcp 'https://futbolatlas.app/mcp?via=manifest'
# 2 — ask your agent for something these tools do
# search, get_entity, get_topic and 6 more
Football Atlas costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http football-atlas-mcp 'https://futbolatlas.app/mcp?via=manifest'Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Full-text search over the knowledge graph. Matching ignores accents and apostrophes, so query in the user's own words; every hit carries the fields it matched and a score. BM25 relevance: each query term is weighted by how RARE it is in this corpus and by where it hits (name 3, tags 2, questions 2, body 1). A hit must also cover a minimum share of the question's information, measured in the same r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, in the user's own words. Matched against titles, questions, claim text and tags; accents and apostrophes are ignored, so 'jose' finds 'José'. |
| limit | integer | no | How many ranked hits to return, best first. |
Fetch one knowledge object by id, with its claims and the sources each claim cites. Use this once search, answer or get_topic has given you an id. An unknown id is not a dead end: the answer names near-miss ids you can retry with.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The knowledge object's id, as returned by search, answer, get_topic or get_related — the last segment of its canonical URL. |
List the knowledge objects carrying a tag (topics are content-backed tags). PAGED: 25 objects by default, 200 at most, and a response budget of about 64 KB per call — a page over budget comes back shorter WITH a next_cursor, never truncated. Read next_cursor and call again to continue, and its absence means you have the last page. Use this to browse a known topic; use search when you have a questi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | yes | The topic to list, spelled exactly as get_overview publishes it. Every published topic has objects under it, so an empty answer means the topic does not exist. |
| limit | integer | no | How many objects to return. Defaults to 25. |
| cursor | string | no | Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one. |
Answer a question from the corpus, or refuse. Returns only the claims that bear on the question, each with the sources it cites and its editorial confidence. When the corpus cannot answer, answered is false and abstention_reason plus missing_topics say what was not covered — a refusal is a real result here, not an error. Use this when the user asked a question in words; use search when you want to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question to answer, in the words the user asked it. |
The instance's source registry — each entry with its evidence tier, reliability and access date. PAGED: 25 entries by default, 200 at most, and a response budget of about 64 KB per call — a page over budget comes back shorter WITH a next_cursor, never truncated. Read next_cursor and call again to continue; its absence means you have the last page. Filter by object_id, tier, host or accessed_since
| Parameter | Type | Required | Notes |
|---|---|---|---|
| object_id | string | no | Restrict the answer to the sources cited by this knowledge object. Omit it to page the whole registry. |
| tier | string | no | Only sources of this evidence tier, spelled exactly as get_sources reports it. |
| host | string | no | Only sources whose URL is served by this host, compared without a leading www. A source with no URL never matches. |
| accessed_since | string | no | Only sources accessed on or after this ISO date (YYYY-MM-DD). |
| limit | integer | no | How many entries to return. Defaults to 25. |
| cursor | string | no | Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one. |
Graph neighbours of an object: outgoing and incoming relations, each with its relation type. PAGED: 25 relations by default, 200 at most, and a response budget of about 64 KB per call — a page over budget comes back shorter WITH a next_cursor, never truncated. One cursor walks both directions, outgoing first; its absence means you have the last page. Use this after get_entity to widen an answer wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The knowledge object to walk out from, by id. |
| limit | integer | no | How many relations to return, across both directions. Defaults to 25. |
| cursor | string | no | Continue from a previous call: pass the next_cursor it returned. Opaque; do not construct one. |
Most recently verified knowledge objects (freshness signal). Use this to judge how current the corpus is, or to see what changed since you last read it. It ranks by verification date and ignores your topic entirely — use search or get_topic when you want objects that are relevant rather than recent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many recently verified objects to return, newest verification first. |
Corpus overview: what this instance knows, counts by type, published tags, freshness. Use this first when you land here and do not yet know whether this corpus can answer your question.
No parameter schema on file.
Two to six knowledge objects side by side: their cards, every indexed attribute as a matrix (the same fields api/index.json publishes, null where an object does not say), the tags they share, the relations that run between them, the neighbours they have in common, and each one's claims with sources and confidence. Use this when the question is 'X vs Y', 'is X the same as Y' or 'how does X differ f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Two to six knowledge object ids, as returned by search, get_topic or get_related, in the order you want the columns. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Football Atlas or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.6.14.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Football Atlas can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.