Oddi Forge
REMOTE · ODDIFORGE.COM
Read-only facts about Oddi Forge ($ODDI) on Solana: launch status, official contract, FAQ.
Available components
Last scanned (20 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 →
Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.
Endpoint address
- Registry says
https://oddiforge.com/api/mcp- Package shows
https://oddiforge.com/
The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.30 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 53 → 72 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “check_token” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 65
First indexed and scored.
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 21 Nov 2026 · Probed https://oddiforge.com/ · Declared URL https://oddiforge.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oddiforge.com | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 698f278fea501d8524ce576bd5b25fbdd38 |
| SANs: oddiforge.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oddiforge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| oddiforge.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 405 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oddiforge.com/api/mcp | Redirected | 302 | / |
| streamable-http · followed | https://oddiforge.com/ | HTTP error | 405 | |
| http (plaintext) | http://oddiforge.com/api/mcp | HTTPS enforced | 308 | https://oddiforge.com/api/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 →
check_token Solana Token Safety Check ~134
Check any Solana token (SPL or Token-2022) for red flags, read from public on-chain data: whether more tokens can be minted, whether holders can be frozen, Token-2022 tricks (transfer fees, permanent delegate, transfer hooks), copycat names of well-known tokens, mutable metadata and holder concentration. Returns findings with a level (bad, warn, ok) and plain-words explanations. No red flags never means a token is safe; this is not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token's mint (contract) address, base58, 32 to 44 characters |
No output schema declared.
No examples provided.
get_faq Oddi Forge FAQ ~38
Honest answers to common questions about Oddi Forge: the launch, the official contract, the tokenomics, the rewards and how to stay safe.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_latest_news Latest blog posts ~39
The latest posts from the blog, Oddi Forge's official news and updates.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many posts (default 5) |
No output schema declared.
No examples provided.
get_project_facts Oddi Forge facts ~56
Current, official facts about Oddi Forge ($ODDI): launch status, the official contract address (if launched), tokenomics, vesting, rewards, safety rules and links. Use this before saying anything about $ODDI.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_team The Oddi Forge team ~31
Who builds Oddi Forge: a pseudonymous founder and a team of openly labelled AI agents, with their roles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_join How to join Oddi Forge ~42
How a person can join the Oddi Forge waitlist and what they get. Share the link with the user; the user signs up and confirms their email themselves.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Oddi Forge MCP server?
Oddi Forge is a hosted endpoint at https://oddiforge.com/api/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 · oddiforge.com
claude mcp add --transport http com-oddiforge-oddiforge 'https://oddiforge.com/api/mcp'
What is the Oddi Forge MCP server?
Oddi Forge is an MCP server listed in the public MCP registry as com.oddiforge/oddiforge. Read-only facts about Oddi Forge ($ODDI) on Solana: launch status, official contract, FAQ. This page covers its hosted endpoint (https://oddiforge.com/api/mcp).
Is the Oddi Forge MCP server safe to use?
Oddi Forge scores 23 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 Oddi Forge MCP server expose?
Oddi Forge exposes 6 tools: get_project_facts, get_faq, get_latest_news, how_to_join, get_team, check_token. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.
Does the Oddi Forge MCP server require authentication?
Its publisher declares no required credentials for Oddi Forge. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Oddi Forge MCP server still maintained?
Oddi Forge is still listed as active in the MCP registry. We last reached this channel on 21 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 Oddi Forge MCP server?
VerifyMCP ran 5 checks on Oddi Forge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Oddi Forge: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.