mcp server
MeatSpace
Human-in-the-loop for AI agents. Submit choices, get a human decision.
Description as published by the maintainer. Source
- version 0.1.0
- slowing
slowing — Registry entry last updated 2026-05-07.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
ask_human(title, run_id, choices, content, metadata, trace_id, agent_name, confidence, callback_url, content_type, decision_reason, timeout_seconds, recommended_option, consequence_of_wrong_choice)- 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. Required: agent_name, title, choices.
get_service_status- Check whether MeatSpace is available and when to use a human. Call this when deciding whether to escalate a subjective or high-consequence choice.
provision_api_key(name, email)- 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. Required: name, email.
Last successful function declaration observed on . Source: https://meatspace.run/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://meatspace.run/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-07 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-07 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | meatspace.run | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | meatspace.run |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json