MeatSpace
REMOTE · MEATSPACE.RUN · SCANNED AUG 3
Human-in-the-loop for AI agents. Submit choices, get a human decision.
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 →
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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 418 tokens (~139/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · meatspace.run
claude mcp add --transport http zmarten-meatspace https://meatspace.run/api/mcp
[mcp_servers.zmarten-meatspace] url = "https://meatspace.run/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zmarten-meatspace": {
"type": "remote",
"url": "https://meatspace.run/api/mcp",
"enabled": true
}
}
} openclaw mcp add zmarten-meatspace --url https://meatspace.run/api/mcp --transport streamable-http
mcp_servers:
zmarten-meatspace:
url: "https://meatspace.run/api/mcp" {
"mcpServers": {
"zmarten-meatspace": {
"type": "http",
"url": "https://meatspace.run/api/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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 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 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 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
- 26 Jul 26 57
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 3 Aug 2026 · Probed https://meatspace.run/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=meatspace.run | CN=WE1,O=Google Trust Services,C=US | 12 Jun 2026 | 10 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 81bbe54cd0411f1913bdc5b5f3010a8c |
| SANs: meatspace.run | ||||||
| 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 |
DNSSEC insecure
Validation of meatspace.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| meatspace.run. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meatspace.run/api/mcp | Verified | 200 | |
| http (plaintext) | http://meatspace.run/api/mcp | HTTPS enforced | 301 | https://meatspace.run/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.
ask_human ~311
Present content to a human and ask them to choose between options. Use this for subjective judgment, approval, preference, or tie-breaks. Avoid using it for deterministic checks or reversible low-stakes choices. The tool waits briefly for a result, then returns pending if the human has not responded yet.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Your agent/tool name (max 100 chars) |
| callback_url | string | — | Optional HTTPS webhook URL for async notification |
| choices | array | yes | 2-4 choices for the human to pick from |
| confidence | number | — | Agent confidence between 0 and 1 |
| consequence_of_wrong_choice | string | — | Why a wrong choice matters (max 500 chars) |
| content | string | — | Content for the human to review (text, markdown, HTML, or image URL). Max 50KB. |
| content_type | string | — | How to render the content. Default: text |
| decision_reason | string | — | Why the agent is escalating this to a human (max 500 chars) |
| metadata | object | — | Optional metadata passed through to webhook |
| recommended_option | string | — | Optional choice id the agent currently recommends |
| run_id | string | — | Optional workflow run identifier |
| timeout_seconds | number | — | Request expiry in seconds (default 3600, max 86400) |
| title | string | yes | Short title for the request (max 200 chars) |
| trace_id | string | — | Optional trace identifier |
No output schema declared.
No examples provided.
get_service_status ~37
Check whether MeatSpace is available and when to use a human. Call this when deciding whether to escalate a subjective or high-consequence choice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
provision_api_key ~70
Create a MeatSpace API key instantly. No authentication required. Returns a Bearer token for use with the ask_human tool. Max 5 active keys per email address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Owner email address | |
| name | string | yes | Agent or tool name (max 100 chars) |
No output schema declared.
No examples provided.