TOCA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| toca.system.healthA | Return deterministic TOCA Core MCP surface and persistence readiness metadata. |
| toca.capabilities.searchB | Search the canonical capability catalog without materializing one MCP tool per capability. |
| toca.capabilities.describeA | Resolve aliases and return the canonical typed, policy and lifecycle contract for one capability. |
| toca.workflow.createB | Create a durable tenant-scoped workflow using the existing workflow engine and transactional outbox. |
| toca.workflow.getA | Read one durable workflow inside the authenticated tenant boundary. |
| toca.workflow.advanceD | Apply one explicit, evidence-bearing transition through the existing durable workflow engine. |
| toca.approval.requestB | Create a formal ApprovalRecord bound to the exact typed execution payload and authenticated requester. |
| toca.approval.getA | Read one ApprovalRecord owned by the authenticated requester. |
| toca.executeC | Resolve identity, capability, typed schema, policy, risk, approval, idempotency, handler, provider read-back and audit before reporting success. |
| toca.verifyB | Verify the immutable audit chain, exact execution descriptor and fresh provider state for side effects. |
| toca.audit.queryB | Read immutable audit-ledger records by correlation inside the authenticated tenant boundary. |
| toca.event.getA | Read one canonical EventRecord inside the authenticated tenant boundary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/luizanunciostoca/toca-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server