io.github.cyanheads/oeis-mcp-server
REMOTE · OEIS.CASEYJHAND.COM · 2 COMPONENTS
Identify integer sequences by terms, search the OEIS, read formulas, programs, b-files, cross-refs.
Available components
Last scanned (8 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1801 tokens (~300/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
- Tool “oeis_get_terms” rewrote its description, which is the text the model reads security
- Server version: 0.1.2 → 0.1.3 functional
- “oeis_search_sequences” reworded the description of “query” cosmetic
- “oeis_get_terms” reworded the description of “limit” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://oeis.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 995a30681ab772540e934241ca1d576c |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of oeis.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| caseyjhand.com. | DS published | 2371 | 13 | Verified |
| oeis.caseyjhand.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oeis.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://oeis.caseyjhand.com/mcp | HTTPS enforced | 301 | https://oeis.caseyjhand.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oeis_get_cross_refs Get OEIS Cross-References ~237
List sequences related to an OEIS entry. direction outgoing returns the A-numbers named in the entry's cross-reference (Cf.) lines, with any parenthetical note beside each; direction incoming returns entries that mention this A-number anywhere. Each row carries the related sequence's name and first terms. 10 rows per page.
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | yes | OEIS A-number, e.g. "A000045"; oeis_identify_sequence and oeis_search_sequences return them. Also accepts "a000045", "A45", "45", and an oeis.org sequence URL; all normalize to the zero-padded form.… |
| direction | string | – | outgoing (default): the A-numbers this entry cross-references. incoming: the entries that mention this A-number. |
| start | integer | – | Row offset: 0, 10, … 100 (at most 110 rows are reachable per entry and direction). Pass nextStart from the previous page. |
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | – | The entry whose relations are listed, e.g. "A000045". |
| cap | number | – | Page size: 10, fixed by OEIS. |
| direction | string | – | The direction listed. |
| effectiveQuery | string | – | The query as OEIS parsed it (lowercased upstream), e.g. seq:1,2,5,14,42. |
| error | object | – | Present when the call failed. Absent on success. |
| lines | array | – | Outgoing only: the entry's cross-reference lines verbatim, written by OEIS contributors; lineIndex points into this list. |
| nextStart | number | – | Pass as start for the next page; absent on the last reachable page. |
| notice | string | – | Guidance: why nothing matched, how to narrow the query, or how to reach the next page. |
| related | array | – | Related sequences on this page: outgoing in order of first mention, incoming in OEIS relevance order. |
| shown | number | – | Rows on this page. |
| start | number | – | The row offset of this page. For incoming, as OEIS served it: below the requested start when that start was past the last entry (OEIS then serves the last page). |
| totalCount | number | – | Total rows: the match count OEIS reported, or for outgoing cross-references the number of distinct A-numbers the entry names. |
| truncated | boolean | – | True when more rows exist than this page shows. |
No examples provided.
oeis_get_sequence Get OEIS Sequence ~356
Fetch one OEIS entry by A-number. Returns the name, data-line terms, offset, keywords, author, dates, and the sections: comments, formulas (recurrences and generating functions), examples, programs (Maple, Mathematica, PARI, Python, …), references, links, cross-references, and extensions. When the sections together exceed 24,000 characters of serialized JSON, the core fields come back with a section outline instead; call again with sections to pick what to read. A selection past 100,000 bytes comes back in parts cut between items: pass nextFromItem as fromItem, with the same sections, for the next part.
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | yes | OEIS A-number, e.g. "A000045"; oeis_identify_sequence and oeis_search_sequences return them. Also accepts "a000045", "A45", "45", and an oeis.org sequence URL; all normalize to the zero-padded form.… |
| fromItem | object | – | Where to resume a cut selection: the previous response's nextFromItem, passed unchanged with the same sections. The selected sections before fromItem.section are left out. Omit to start at the beginn… |
| sections | array | – | Sections to return with the core fields, e.g. ["formulas", "programs"]. A selection past the 100,000-byte response budget is cut between items; fromItem continues it. Omit (or pass []) for the full e… |
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | – | A-number, e.g. "A000045". |
| author | string | – | Author line as OEIS records it; absent when the entry has none. |
| bFileUrl | string | – | URL of the entry's b-file of extended terms; oeis_get_terms reads it. |
| comments | array | – | Comment lines, one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only this part's lines. |
| created | string | – | When the entry was created, ISO 8601 with offset. |
| crossReferences | array | – | Cross-reference lines naming related A-numbers, one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only this part's lines. |
| error | object | – | Present when the call failed. Absent on success. |
| examples | array | – | Example lines; whitespace matters for triangles and tables, one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only this pa… |
| extensions | array | – | Extension lines: who added terms or corrections, and when, one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only this par… |
| firstIndex | number | – | The index n of the first term (the first number of offset); absent with offset. |
| formulas | array | – | Formula lines: recurrences, generating functions, closed forms, one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only thi… |
| keywords | array | – | Keyword flags such as nonn, core, tabl; oeis_list_reference topic keywords decodes them. |
| kind | string | – | full: every section, or the selected ones (a selection past the 100,000-byte response budget is cut between items, and nextFromItem continues it). outline: the entry is too large, so sections lists t… |
| legacyIds | array | – | Legacy book numbers, e.g. ["M0692", "N0256"]; absent on entries that have none. |
| links | array | – | Link lines. Present on a full entry or when selected; a cut selection carries only this part's lines. |
| modified | string | – | When the entry was last edited, ISO 8601 with offset. |
| name | string | – | Sequence name, written by OEIS contributors. |
| nextFromItem | object | – | Present when the selection was cut at the 100,000-byte response budget: the first item left out. Pass it unchanged as fromItem, with the same sections, to continue. |
| notice | string | – | Guidance: the entry is withdrawn (dead) or its A-number reserved or recycled; where a cut selection stopped and the call that continues it; or that fromItem lies past the end of its section. |
| offset | string | – | Offset "i,p": i is the index n of the first term, p the 1-based position of the first term with |a(n)| > 1. Absent on a reserved or recycled A-number (keyword allocated or recycled). |
| outlineNotice | string | – | Outline only: how to request sections, and how a large selection continues. |
| programs | array | – | Programs that compute the terms. Present on a full entry or when selected; a cut selection carries only this part's blocks. |
| referenceCount | number | – | How many OEIS entries mention this A-number, the entry itself included. |
| references | array | – | Reference lines (books and papers), one element per upstream line, written by OEIS contributors. Present on a full entry or when selected; a cut selection carries only this part's lines. |
| revision | number | – | Revision number of the entry. |
| sections | array | – | Outline only: the sections of the entry, largest first. |
| terms | array | – | Data-line terms as exact decimal strings, signs kept; the first is a(firstIndex). |
| url | string | – | Sequence page on oeis.org; cite it wherever the entry is reused. |
No examples provided.
oeis_get_terms Get OEIS Sequence Terms ~306
List terms a(n) of a sequence with their indices n. Reads the entry's b-file when it has one — often thousands of terms beyond the data line — and otherwise the data line itself. Values are exact decimal strings of any size. A slice stops at limit terms (at most 1000 per call), at about 100,000 bytes, or at the end of one 1 MiB part of a larger b-file, whichever comes first; nextFromIndex continues it.
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | yes | OEIS A-number, e.g. "A000045"; oeis_identify_sequence and oeis_search_sequences return them. Also accepts "a000045", "A45", "45", and an oeis.org sequence URL; all normalize to the zero-padded form.… |
| fromIndex | integer | – | First index n to return; defaults to the first available index. Pass nextFromIndex from the previous call to continue. |
| limit | integer | – | Maximum number of terms to return (default 100). One call returns at most 1000, so a larger limit is served as 1000. A slice stops sooner at about 100,000 bytes of large terms or at the end of one 1… |
| Name | Type | Req | Description |
|---|---|---|---|
| aNumber | string | – | A-number, e.g. "A000045". |
| bFileCut | boolean | – | True while the b-file goes on past lastAvailableIndex. Its later terms are at bFileUrl; nextFromIndex or a larger fromIndex reaches them unless the notice says only the first 1 MiB was read. |
| bFileSizeInBytes | number | – | Full size of the b-file as OEIS reported it; absent when not reported. |
| bFileUrl | string | – | URL of the b-file the terms came from; absent when source is data. |
| cap | number | – | The limit that was applied: limit, or 1000 when limit is larger. |
| error | object | – | Present when the call failed. Absent on success. |
| firstAvailableIndex | number | – | Lowest index n read for this entry; absent when no terms were read. |
| lastAvailableIndex | number | – | Highest index n read so far for this entry; when bFileCut is true the b-file goes on past it. Absent when no terms were read. |
| nextFromIndex | number | – | Pass as fromIndex for the next slice. Absent when no slice follows this one: the terms ended, or the notice says how to reach the rest. |
| notice | string | – | Guidance: where the next slice starts and whether the byte budget ended this one, why no terms came back (past the last index, or not yet reached in a large b-file), that a b-file line too long to re… |
| shown | number | – | Terms in this slice. |
| source | string | – | bfile: read from the entry's b-file of extended terms. data: the entry has no b-file, so these are its data-line terms. |
| terms | array | – | Terms in index order, from the first index at or after fromIndex (or the first available index). |
| truncated | boolean | – | True when nextFromIndex is set. |
| url | string | – | Sequence page on oeis.org; cite it wherever the terms are reused. |
No examples provided.
oeis_identify_sequence Identify OEIS Sequence ~298
Identify integer sequences that contain a run of consecutive terms, e.g. "1, 2, 5, 14, 42". Returns up to 10 matches per page in OEIS relevance order, each with the index n at which the supplied run begins. For the best hit rate supply about 6 terms and leave off the first one or two, since sources disagree on where a sequence starts. OEIS matches only the first terms of each entry (its data line, at most about 270 characters), not its b-file, so a run from far into a sequence is not found. Takes up to 60 terms, each an integer of at most 200 digits or the wildcard _ for one unknown term.
| Name | Type | Req | Description |
|---|---|---|---|
| matchSigns | boolean | – | false (default) matches ignoring signs, so a sign-convention difference does not hide the sequence; true requires the signs to match. |
| start | integer | – | Result offset: 0, 10, … 100 (OEIS shows at most 110 results per query). Pass nextStart from the previous page. |
| terms | string | yes | Up to 60 consecutive terms separated by commas or spaces, e.g. "1, 2, 5, 14, 42" (a bracketed list or a trailing ... is accepted). Each term is an integer of at most 200 digits, or _ for a single unk… |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | Page size: 10, fixed by OEIS. |
| effectiveQuery | string | – | The query as OEIS parsed it (lowercased upstream), e.g. seq:1,2,5,14,42. |
| error | object | – | Present when the call failed. Absent on success. |
| nextStart | number | – | Pass as start for the next page; absent on the last reachable page. |
| notice | string | – | Guidance: why nothing matched, how to narrow the query, or how to reach the next page. |
| results | array | – | Candidate sequences on this page, in OEIS relevance order. |
| shown | number | – | Rows on this page. |
| start | number | – | The result offset of this page as OEIS served it; below the requested start when that start was past the last result (OEIS then serves the last page). |
| totalCount | number | – | Total rows: the match count OEIS reported, or for outgoing cross-references the number of distinct A-numbers the entry names. |
| truncated | boolean | – | True when more rows exist than this page shows. |
No examples provided.
oeis_list_reference List OEIS Reference ~123
Look up OEIS vocabulary used by the other tools: keyword flags (nonn, core, tabl, cons, …), search syntax (prefixes, operators, wildcards, sort orders, paging window), and identifier conventions (A-numbers, legacy M/N numbers, offsets, b-files).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | keywords: keyword flags such as nonn, core, tabl. search_syntax: prefixes, operators, wildcards, sort orders, and paging. identifiers: A-numbers, legacy M/N numbers, offsets, and b-files. |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | – | Vocabulary entries for the topic. |
| error | object | – | Present when the call failed. Absent on success. |
| notes | array | – | Usage notes that apply across the topic. |
| topic | string | – | The topic listed. |
No examples provided.
oeis_search_sequences Search OEIS Sequences ~250
Search the OEIS using its query syntax: plain words, "quoted phrases", comma-separated terms, prefixes (keyword:, author:, name:, comment:, formula:, program:, xref:, id:), | for OR, and a leading - to exclude. Returns up to 10 summaries per page. For identifying a sequence from its terms, oeis_identify_sequence is the direct route.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | OEIS query, sent as written. Examples: keyword:core fibonacci; author:Sloane; "Catalan numbers" (a quoted phrase); 1,2,5,14,42 (separate terms with commas: with spaces alone, a negative term after th… |
| sort | string | – | Result order: relevance (default), number (ascending A-number), created (newest entry first), or modified (most recently edited first). |
| start | integer | – | Result offset: 0, 10, … 100 (OEIS shows at most 110 results per query). Pass nextStart from the previous page. |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | Page size: 10, fixed by OEIS. |
| effectiveQuery | string | – | The query as OEIS parsed it (lowercased upstream), e.g. seq:1,2,5,14,42. |
| error | object | – | Present when the call failed. Absent on success. |
| nextStart | number | – | Pass as start for the next page; absent on the last reachable page. |
| notice | string | – | Guidance: why nothing matched; that OEIS split the numbers into separate searches, and how to join them with commas into one run; how to narrow the query; or how to reach the next page. |
| results | array | – | Matching sequences on this page, in the applied order. |
| shown | number | – | Rows on this page. |
| sort | string | – | The result order applied. |
| start | number | – | The result offset of this page as OEIS served it; below the requested start when that start was past the last result (OEIS then serves the last page). |
| totalCount | number | – | Total rows: the match count OEIS reported, or for outgoing cross-references the number of distinct A-numbers the entry names. |
| truncated | boolean | – | True when more rows exist than this page shows. |
No examples provided.
How do I install the io.github.cyanheads/oeis-mcp-server server?
io.github.cyanheads/oeis-mcp-server is a hosted endpoint at https://oeis.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · oeis.caseyjhand.com
claude mcp add --transport http cyanheads-oeis-mcp-server 'https://oeis.caseyjhand.com/mcp'
What is the io.github.cyanheads/oeis-mcp-server server?
io.github.cyanheads/oeis-mcp-server is listed in the public MCP registry as io.github.cyanheads/oeis-mcp-server. Identify integer sequences by terms, search the OEIS, read formulas, programs, b-files, cross-refs. This page covers its hosted endpoint (https://oeis.caseyjhand.com/mcp).
Is the io.github.cyanheads/oeis-mcp-server server safe to use?
io.github.cyanheads/oeis-mcp-server scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cyanheads/oeis-mcp-server server expose?
io.github.cyanheads/oeis-mcp-server exposes 6 tools: oeis_identify_sequence, oeis_search_sequences, oeis_get_sequence, oeis_get_terms, oeis_get_cross_refs, oeis_list_reference. Their descriptions and schemas cost roughly 1,570 tokens of context every time the server is loaded.
Does the io.github.cyanheads/oeis-mcp-server server require authentication?
No. We connected to io.github.cyanheads/oeis-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/oeis-mcp-server server still maintained?
io.github.cyanheads/oeis-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.cyanheads/oeis-mcp-server server?
VerifyMCP ran 13 checks on io.github.cyanheads/oeis-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.