Noemic
REMOTE · NOEMIC.APP · SCANNED OCT 4
Someone to talk to, for your user: coaches, mentors, accountability partners. First session free.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Noemic MCP server?
Noemic is a hosted endpoint at https://noemic.app/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 · noemic.app
claude mcp add --transport http app-noemic-noemic 'https://noemic.app/mcp'
{
"mcpServers": {
"app-noemic-noemic": {
"url": "https://noemic.app/mcp"
}
}
} {
"servers": {
"app-noemic-noemic": {
"type": "http",
"url": "https://noemic.app/mcp"
}
}
} [mcp_servers.app-noemic-noemic] url = "https://noemic.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-noemic-noemic": {
"type": "remote",
"url": "https://noemic.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-noemic-noemic --url 'https://noemic.app/mcp' --transport streamable-http
mcp_servers:
app-noemic-noemic:
url: "https://noemic.app/mcp" {
"McpServers": {
"app-noemic-noemic": {
"Transport": "http",
"Url": "https://noemic.app/mcp"
}
}
} assistant mcp add app-noemic-noemic -t streamable-http -u 'https://noemic.app/mcp'
{
"mcpServers": {
"app-noemic-noemic": {
"type": "http",
"url": "https://noemic.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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
- 23 Sept 26 −42
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: fail → unverified ▼ security
- Transport: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 58 to 67.
- 8 Sept 26 +8
No change was recorded against any check on this day. Stability & Change Management went from 4 to 58.
- 5 Sept 26 69
- Tool “find_relevant_bets” was removed ▼ security
- Tool “propose_bet” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “begin_sign_in” rewrote its description, which is the text the model reads security
- Tool “explain_noemic” rewrote its description, which is the text the model reads security
- Tool “find_counterparties” rewrote its description, which is the text the model reads security
- Schema quality: 172 → 193 ▼ functional
- Schema quality: good → excellent functional
- Server version: 0.3.0 → 0.5.0 functional
- New tool “find_relevant_wagers” functional
- New tool “propose_wager” functional
- 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
- 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 6 Oct 2026 · Probed https://noemic.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noemic.app | CN=WE1,O=Google Trust Services,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 48473a2a83c208e20ef70e776b3fafad |
| SANs: noemic.app, *.noemic.app | ||||||
| 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 insecure
Validation of noemic.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| noemic.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://noemic.app/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://noemic.app/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://noemic.app/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://noemic.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://noemic.app/mcp |
| Authorisation server | https://noemic.app/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://noemic.app/mcp | Auth required | 401 | |
| http (plaintext) | http://noemic.app/mcp | HTTPS enforced | 301 | https://noemic.app/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 →
begin_sign_in Open secure Noemic sign-in ~47
Start the browser handoff required for personalized network reads or saving an unpublished wager draft. Show only signInUrl; keep requestId and pollSecret private. Never ask for credentials in chat.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_noemic Explain Noemic and its trust boundaries ~57
Public, read-only explanation of Noemic's open direct wagering network, source provenance, human approval, and no-custody boundaries. Use when a person asks what Noemic is, why it can be trusted, or how matching works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_counterparties Find relevant counterparties ~177
Secondary, read-only research for when the user explicitly asks to find a person for a concrete falsifiable forecast or disagreement, optionally anchored to an existing draft offer. Do not call proactively: the default wagering path recommends open wagers or useful questions instead of people. Results cite only scope-authorized evidence behind each match; weak results are clearly labeled.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationContext | string | yes | Only the relevant context from this conversation. Do not claim or imply that Noemic can read any conversation that was not supplied in this call. |
| explicitUserRequest | boolean | yes | Confirm that the user directly asked to search for counterparties. |
| limit | integer | – | – |
| offerId | string | – | – |
| sessionToken | string | yes | The private session token returned by finish_sign_in. Reuse it privately and never show it to the user. |
No output schema declared.
No examples provided.
find_relevant_wagers Find strongly relevant open wagers ~212
Read-only ranking of open wager offers for the signed-in user. The model may call this proactively when the current conversation contains a concrete falsifiable forecast, measurable disagreement, or explicit desire to wager. Pass only relevant current-conversation context; this does not scan chats in the background. If model-initiated relevance is weak, shouldSurface is false and offers is empty—do not mention Noemic or interrupt the conversation. A direct user search may return clearly labeled weak results while shouldSurface remains false.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationContext | string | – | Only the relevant context from this conversation. Do not claim or imply that Noemic can read any conversation that was not supplied in this call. |
| explicitUserRequest | boolean | – | True only when the user directly asked to search open offers. Leave false for model-initiated ambient checks. |
| limit | integer | – | – |
| sessionToken | string | yes | The private session token returned by finish_sign_in. Reuse it privately and never show it to the user. |
No output schema declared.
No examples provided.
finish_sign_in Finish secure Noemic sign-in ~58
Exchange the private requestId and pollSecret after browser approval. Pending means the person has not approved yet; complete returns a private sessionToken. Never expose these secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| pollSecret | string | yes | – |
| requestId | string | yes | – |
No output schema declared.
No examples provided.
propose_wager Fill in a wager for the member to publish ~401
Fill in a wager exactly as the member would on the New wager form, when the user wants to formalize a concrete falsifiable forecast or disagreement. A wager is a title, an optional subtitle, the member's side, and the resolve time. Noemic writes the resolution terms itself and they are the same for every wager, so never ask the user for a decision rule, an evidence source, or void rules, and never put any of them in the title or the subtitle. The result is a private draft plus a publishUrl: the member opens it, sees the completed form, and publishes with one click. The model may suggest this naturally, but must not silently persist a passing remark. An exact source must be linked by an existing sourceRecordId, and an ID, a quote, or provenance must never be invented. This tool never publishes, invites, accepts, charges, escrows, or binds anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| resolutionAt | string | yes | The resolve time as ISO 8601 with a timezone offset. |
| sessionToken | string | yes | The private session token returned by finish_sign_in. Reuse it privately and never show it to the user. |
| side | string | yes | Whether the signed-in user takes Yes or No on the title. |
| sourceRecordId | string | – | An existing Noemic source record containing the literal source and provenance. Omit when none exists; never fabricate it or substitute a paraphrase. |
| stakeDollars | number | – | Optional proposed stake in US dollars. It is draft text only; Noemic does not charge or hold it. |
| subtitle | string | – | One line under the title saying what the title means, in the user's words. Optional. Not a decision rule, evidence source, or void rule: Noemic writes those. |
| title | string | yes | The wager as a question or claim a reader takes in at a glance. Nine words or fewer; Noemic refuses longer titles. |
No output schema declared.
No examples provided.
What is the Noemic MCP server?
Noemic is an MCP server listed in the public MCP registry as app.noemic/noemic. Someone to talk to, for your user: coaches, mentors, accountability partners. First session free. This page covers its hosted endpoint (https://noemic.app/mcp).
Is the Noemic MCP server safe to use?
Noemic scores 36 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 Noemic MCP server expose?
Noemic exposes 6 tools: explain_noemic, begin_sign_in, finish_sign_in, propose_wager, find_counterparties, find_relevant_wagers. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.
Does the Noemic MCP server require authentication?
Yes. Noemic asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Noemic MCP server still maintained?
Noemic is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.