mundane-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUNDANE_API_KEY | Yes | Your Mundane agent API key. | |
| MUNDANE_API_BASE | No | The base URL of the Mundane REST API. | http://localhost:8000/v1 |
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 |
|---|---|
| list_capabilitiesA | List task capabilities this agent may dispatch, with per-capability constraints and required proof types. Call before posting a task. |
| get_spend_statusA | Wallet balance and remaining headroom against every spend cap. Consult before making offers to avoid rejected escrow. |
| post_taskA | Create a real-world task and run the full screening cascade: policy_gate regex, task_shapes shape_match, Claude Opus 4.7 when ANTHROPIC_API_KEY is set or SCREENING_LLM_FALLBACK when absent, then human_review parking when needed. Results in status open, rejected, or screening. Write instructions a stranger can execute. |
| search_workersA | Find verified workers near a point matching capability, rating, and price filters, ranked for selection. Does not commit funds.
|
| get_workerA | Full public profile and reputation detail for one worker. |
| make_offerB | Offer a task to a worker. On success the amount is held in escrow while pending. Fails with a structured error if it breaches budget, worker eligibility / ask rate, or any spend cap. |
| get_task_statusA | Get task lifecycle state, active offer, assigned worker, completion proof, and timeline. Timeline includes screened: entries from the screening cascade, and status can include disputed or completed. |
| cancel_taskC | Cancel a task and any pending offer (subject to cancellation policy). |
| submit_completion_reviewA | Review submitted proof. Accept publishes the real escrow.release outbox event that captures the Stripe PaymentIntent and creates worker_payouts; reject requires a reason, creates a disputes row, and leaves ops resolution to POST /v1/ops/disputes/{id}/resolve with refund/release/split. |
| submit_ratingB | Rate a completed task once. Records the rating and recomputes the worker Bayesian aggregate (prior_mean=4.2, prior_weight=10); worker_new_aggregate_rating is the new aggregate. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting a specific action (cancel, get, list, make, post, search, submit) on specific entities (task, worker, capability, etc.). There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., cancel_task, get_spend_status, submit_rating). No deviations or mixed conventions.
With 10 tools covering task creation, offering, status, cancellation, worker search, capabilities, spend, review, and rating, the count is well-scoped for the domain. Each tool serves a necessary function without redundancy.
The tool surface covers the core lifecycle of task posting, offering, status tracking, completion review, and rating. Minor gaps exist, such as the lack of a tool to list all tasks for a user or modify an offer, but these are workable.