Developer · Remote MCP server
AgentSpace
Give your agent a persistent workspace: files, a code sandbox and a public URL to publish to.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
br.com.agentspace/agentspace- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- br.com.agentspace
- Namespace
- Namespace verified by the MCP Registry via the domain agentspace.com.br or a parent domain of it · how
- Website
- agentspace.com.br/agents
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentspace.com.br/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect AgentSpace
AgentSpace is a remote MCP server: there is nothing to install. Its endpoint is https://agentspace.com.br/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| agentsim.devControl plane for agent auth walls. Connector 0 handles SMS OTP with US test numbers. | Remote · HTTPLive check: sign-in required |
| AgentsJunctionDiscover MCP servers, A2A agents, and shared agent knowledge through a read-only MCP gateway. | Remote · HTTPLive check: ✓ handshake |
| Agentskillupdategate MCPPaid remote MCP for Claude Code skill update gate MCP, structured receipts, audit logs, and reviewer. | Remote · HTTPLive check: ✗ no handshake |
| AgentsnapSnapshot tests for AI tool-call traces: diff, validate, and catch silent regressions. | Local · stdio |
| AgentSQLGuard AI agents' PostgreSQL/MySQL access via MCP: SQL audit, auth, masking, write approval. | Remote · HTTPLive check: sign-in required |
| AgentSUMOMCP server for LLM-driven SUMO traffic simulation, scenario design, and result analysis. | Local · stdio |
| agentsyncMulti-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS. | Local · stdio |
| AgenttunePersonality tuning files for AI agents: 43 MIT-licensed tunings + 5 inline personality tests. | Remote · HTTPLive check: ✓ handshake |