ArkForge Trust Layer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARKFORGE_API_KEY | Yes | Your ArkForge API key, obtainable from arkforge.tech. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| certify_callA | Call an external API and get a cryptographic proof of the transaction. Use this INSTEAD of calling the API directly when you need an auditable, tamper-evident record of what was sent and received. The proof is signed by ArkForge (independent third party), timestamped via RFC 3161, and anchored in Sigstore Rekor — not self-signed by your agent. Args: target: URL of the upstream API to call (e.g. "https://api.example.com/v1/action") payload: JSON body to send to the upstream API (optional for GET requests) method: HTTP method — "POST" or "GET" (default: "POST") description: Human-readable description of what this call does (included in the proof) agent_identity: Identifier for the calling agent (optional, included in the proof) Returns: JSON with proof_id, verification_url, the upstream API response, chain_hash, and timestamp. Share verification_url with any third party to let them independently verify what happened. |
| get_proofA | Retrieve the full cryptographic proof for a given proof ID. Returns the complete proof bundle: request/response hashes, parties, RFC 3161 timestamp, Sigstore Rekor log entry, and archive.org snapshot. Args: proof_id: The proof identifier (e.g. "prf_20260310_143022_a1b2c3") |
| verify_proofA | Get a human-readable summary of what a proof certifies. Useful for explaining to a user or auditor what was independently verified, without reading raw JSON. Args: proof_id: The proof identifier (e.g. "prf_20260310_143022_a1b2c3") |
| get_usageA | Check your ArkForge API usage and remaining credits for the current period. Returns your tier (Free / Pro / Enterprise), proofs used, proofs remaining, and the reset date. |
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/ark-forge/arkforge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server