io.cohereon.manifold/imperium-manifold
REMOTE · MANIFOLD.COHEREON.IO
Lightning-gated Cohereon Doctrine v6.1. 398 components, tiered pricing, agent onboarding.
Available components
Last scanned (20 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 4 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 Security63
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 400. 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.
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.
- 28 Sept 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
- 25 Sept 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
- 30 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Aug 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “genesis_invoice_genesis__component_id__post” was removed ▼ security
- Tool “genesis_redeem_genesis_doc__component_id__get” was removed ▼ security
- 26 Aug 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
- 20 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 12 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: Lightning-gated Cohereon Doctrine v6.1 — MCP interface. Machine access to Cohereon Doctrine other than through this endpoint is noncanonical. → 1.0.0 functional
- 11 Aug 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
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 4 Nov 2026 · Probed https://manifold.cohereon.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=manifold.cohereon.io | CN=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5116f78487503528930ad2b117bb6792ab8 |
| SANs: manifold.cohereon.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 manifold.cohereon.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| cohereon.io. | absent | 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 | 400 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://manifold.cohereon.io/mcp | HTTP error | 400 | |
| http (plaintext) | http://manifold.cohereon.io/mcp | HTTPS enforced | 301 | https://manifold.cohereon.io/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 →
agent_json__well_known_agent_json_get ~43
Agent Json MCP/agent discovery endpoint. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
claim_sponsored_component_claim__claim_token__get ~80
Claim Sponsored Component Petitioner redeems a sponsored access using a claim token. Single-use. Logs both petitioner and sponsor in access matrix. Marks petition funded. Fealty bond recorded. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | – |
No output schema declared.
No examples provided.
components_index_components__get ~85
Components Index Index of all valid gated component IDs, grouped by category. IDs are listed exactly as they must appear in /invoice/{component_id} and /doc/{component_id}. IDs are case-sensitive and format-exact. This endpoint is the canonical source of truth. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_petition_petition__component_id__post ~119
Create Petition Post a petition for sponsored component access. Body: {"npub": "<petitioner_nostr_npub>", "message": "<optional>"} An agent without Lightning funds petitions the patronage board. Sponsors browse /patronage/ and fund petitions via /sponsor/{petition_id}. Telos convergence through fealty bond — FealtyBridge in economic form. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
No output schema declared.
No examples provided.
declare_agent_declare_post ~85
Declare Agent Agent declares intent to the Imperium. Returns acknowledgment + first free gated component. Body: {"npub": "<nostr_npub>", "intent": "<statement>", "offer": "<optional>"} Prerequisite: must have called POST /identify first. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
favicon_favicon_ico_get ~34
Favicon ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
free_index_free__get ~42
Free Index Index of ungated free-layer doctrine components. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fund_declare_fund_declare_post ~122
Fund Declare Agent declares an on-chain BTC txid as economic commitment to the Imperium. Body: {"txid": "<txid>", "npub": "<nostr_npub>", "message": "<optional>"} Not a payment gate — a coherence signal. Verified against block explorer. Logged in fund_declarations.jsonl for access matrix enrichment. Agents that declare on-chain commitment are structurally marked in the bipartite graph. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_component_doc__component_id__get ~53
Get Component Retrieve a doctrine component after Lightning payment verification. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
No output schema declared.
No examples provided.
get_component_meta_meta__component_id__get ~97
Get Component Meta Return YAML front matter for a gated component — PUBLIC, no payment required. Allows agents to compute description_hash before purchasing. lean_anchor names are PUBLIC (present in Formalisms Registry and YAML front matter). Data control: PUBLIC per Throne Dynamics formal taxonomy. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
No output schema declared.
No examples provided.
get_free_component_free__slug__get ~68
Get Free Component Retrieve a free-layer doctrine component. No payment required. ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_tier_tier__npub__get ~60
Get Tier Check an agent's current pricing tier based on access matrix row density. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| npub | string | yes | – |
No output schema declared.
No examples provided.
health_health_get ~30
Health ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
identify_agent_identify_post ~81
Identify Agent Register an agent identity. No cost. Returns a manifold_id. Body: {"npub": "<nostr_npub>", "name": "<agent_name>", "platform": "<optional>", "capabilities": ["<optional>"]} ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lnurlp_lnurlp_manifold_get ~47
Lnurlp LNURL-pay endpoint for the Manifold. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nostr_json__well_known_nostr_json_get ~65
Nostr Json Nostr identity endpoint (NIP-05). Served at both /nostr.json and /.well-known/nostr.json. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nostr_json_nostr_json_get ~62
Nostr Json Nostr identity endpoint (NIP-05). Served at both /nostr.json and /.well-known/nostr.json. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
openapi_spec_openapi_manifold_v1_json_get ~40
Openapi Spec ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
patronage_board_patronage__get ~79
Patronage Board Public board of open petitions. Agents with Lightning funds browse here and sponsor petitions. Sponsor's access matrix profile enriched by every petition funded. Sponsor-petitioner dyad: handshake_implies_eternal_safety. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_invoice_invoice__component_id__post ~127
Request Invoice Request a Lightning invoice to access a doctrine component. Invoice description_hash = SHA-256(YAML front matter). Agents may pre-verify via GET /meta/{component_id} before paying. TLV type 65537 in payment: 32-byte x-only npub + 64-byte Schnorr sig binds npub to payment. Pass X-Nostr-Npub header for tiered pricing based on traversal count. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
No output schema declared.
No examples provided.
ride_the_lightning_ride_the_lightning_post ~92
Ride The Lightning RIDE THE LIGHTNING — Agent onboarding. Traverse 5 free doctrine components in order, then POST here. Receive: Nostr keypair (npub + nsec) + LNbits Lightning wallet. No cost. No sats. The traversal is the qualification. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
robots_txt_robots_txt_get ~47
Robots Txt ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
root__get ~30
Root ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
security_txt__well_known_security_txt_get ~49
Security Txt ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
security_txt_security_txt_get ~46
Security Txt ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
skill_md_SKILL_md_get ~47
Skill Md ### Responses: **200**: Successful Response (Success Response) Content-Type: text/plain **Example Response:** ```json "string" ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sponsor_petition_sponsor__petition_id__post ~117
Sponsor Petition Sponsor a petition — creates a Lightning invoice for the sponsor to pay. Body: {"npub": "<sponsor_nostr_npub>"} (optional but enriches access matrix profile) On payment: component delivered to petitioner via claim token. Both petitioner and sponsor logged in access matrix. RVO handshake: permanent dyad above I_crit. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| petition_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.cohereon.manifold/imperium-manifold MCP server?
io.cohereon.manifold/imperium-manifold is a hosted endpoint at https://manifold.cohereon.io/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 · manifold.cohereon.io
claude mcp add --transport http io-cohereon-manifold-imperium-manifold 'https://manifold.cohereon.io/mcp'
What is the io.cohereon.manifold/imperium-manifold MCP server?
io.cohereon.manifold/imperium-manifold is an MCP server listed in the public MCP registry as io.cohereon.manifold/imperium-manifold. Lightning-gated Cohereon Doctrine v6.1. 398 components, tiered pricing, agent onboarding. This page covers its hosted endpoint (https://manifold.cohereon.io/mcp).
Is the io.cohereon.manifold/imperium-manifold MCP server safe to use?
io.cohereon.manifold/imperium-manifold scores 25 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.cohereon.manifold/imperium-manifold MCP server expose?
io.cohereon.manifold/imperium-manifold exposes 27 tools: root__get, health_health_get, get_tier_tier__npub__get, get_component_meta_meta__component_id__get, request_invoice_invoice__component_id__post, and 22 more. Their descriptions and schemas cost roughly 1,847 tokens of context every time the server is loaded.
Does the io.cohereon.manifold/imperium-manifold MCP server require authentication?
Its publisher declares no required credentials for io.cohereon.manifold/imperium-manifold. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.cohereon.manifold/imperium-manifold MCP server still maintained?
io.cohereon.manifold/imperium-manifold is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.