API Tools
meatspace.run
Provides tools to interact with MeatSpace, including checking service status, human-in-the-loop decision making, and API key provisioning.
ENDPOINT 1
https://meatspace.run/api/mcp
MCP server metadata
- Name
- meatspace
- Version
- 0.1.0
Known tools 3
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.meatspace]
url = "https://meatspace.run/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"meatspace": {
"type": "http",
"url": "https://meatspace.run/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: meatspace
Remote MCP URL: https://meatspace.run/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"meatspace": {
"url": "https://meatspace.run/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"meatspace": {
"type": "http",
"url": "https://meatspace.run/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "meatspace",
"transport": "streamable-http",
"url": "https://meatspace.run/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for meatspace.run was fetched 2026-07-26T10:24:11.138Z and is being refreshed.
meatspace.run is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.