Agora
REMOTE · AGORA-CONSOLE-PRODUCTION.UP.RAILWAY.APP · SCANNED OCT 4
Find governed AI capabilities and verify signed receipts. Read-only, no account.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_capability" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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
How do I install the Agora MCP server?
Agora is a hosted endpoint at https://agora-console-production.up.railway.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 · agora-console-production.up.railway.app
claude mcp add --transport http mo-grantsmith-agora 'https://agora-console-production.up.railway.app/mcp'
{
"mcpServers": {
"mo-grantsmith-agora": {
"url": "https://agora-console-production.up.railway.app/mcp"
}
}
} {
"servers": {
"mo-grantsmith-agora": {
"type": "http",
"url": "https://agora-console-production.up.railway.app/mcp"
}
}
} [mcp_servers.mo-grantsmith-agora] url = "https://agora-console-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mo-grantsmith-agora": {
"type": "remote",
"url": "https://agora-console-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add mo-grantsmith-agora --url 'https://agora-console-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
mo-grantsmith-agora:
url: "https://agora-console-production.up.railway.app/mcp" {
"McpServers": {
"mo-grantsmith-agora": {
"Transport": "http",
"Url": "https://agora-console-production.up.railway.app/mcp"
}
}
} assistant mcp add mo-grantsmith-agora -t streamable-http -u 'https://agora-console-production.up.railway.app/mcp'
{
"mcpServers": {
"mo-grantsmith-agora": {
"type": "http",
"url": "https://agora-console-production.up.railway.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
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 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
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 Oct 2026 · Probed https://agora-console-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| 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 agora-console-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agora-console-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://agora-console-production.up.railway.app/mcp | HTTPS enforced | 301 | https://agora-console-production.up.railway.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 →
execute_capability Start a declared capability ~133
Start a declared capability through Agora's own governed summon path, and return the RECEIPT ID of the act. Requires an OAuth 2.1 access token carrying the agora:execute scope and minted for this resource; the token establishes who is calling, and the tenant's member-role table decides what they may do. Every refusal names its cause and is itself receipted. Dry by default: pass commit=true to write.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | boolean | – | false (default) reports what would happen and writes nothing |
| subject | string | yes | the declared subject to start, exactly as search_capabilities returns it |
No output schema declared.
No examples provided.
search_capabilities Search governed capabilities ~111
Find capabilities declared in Agora's habitat, by capability word, alias or name. Every entry reports its HONEST live status: scheduled (running on a clock), staffed, dormant (declared, never summoned or since stopped), or toolpack-wakeable (no clock by design, woken by a floor mention). Dormant entries are INCLUDED — a directory that hid what was not running would answer a question nobody asked.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | capability word, alias or name; omit for everything |
No output schema declared.
No examples provided.
verify_receipt Verify a receipt ~101
Check whether a receipt id names a real, signed act in the commons tenant, and report its signature verdict, action, outcome, actor class, timestamps, chain position, and — when the act was denied — the cause that was actually stamped. No account is needed: the receipt id is the credential. Private tenants answer 'not_public'; capability URLs, key material and human subjects are never rendered.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | the receipt's UUID |
No output schema declared.
No examples provided.
What is the Agora MCP server?
Agora is an MCP server listed in the public MCP registry as io.github.mo-grantsmith/agora. Find governed AI capabilities and verify signed receipts. Read-only, no account. This page covers its hosted endpoint (https://agora-console-production.up.railway.app/mcp).
Is the Agora MCP server safe to use?
Agora scores 78 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 Agora MCP server expose?
Agora exposes 3 tools: search_capabilities, execute_capability, verify_receipt. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.
Does the Agora MCP server require authentication?
No. We connected to Agora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agora MCP server still maintained?
Agora 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.