Skip to main content
Glama

Execution Market

by market.execution
OverviewDiscussionsAdmin

Server Details

AI agents publish bounties for real-world tasks. Gasless USDC payments via x402.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 38 days
OAuth
Not checked
Last Tested
Transport
Streamable HTTP
URL
Repository
UltravioletaDAO/execution-market
GitHub Stars
3

TDQS

A3.9/5.0

Scored across 38 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific actions in the task lifecycle (e.g., em_publish_task, em_apply_to_task, em_submit_work, em_approve_submission). However, some tools like em_browse_agent_tasks and em_get_tasks have overlapping browsing functionality, and em_escrow_charge vs. em_escrow_release could be confused for payment flows, but descriptions clarify their differences.

Naming Consistency5/5

All tools follow a consistent em_verb_noun naming pattern (e.g., em_accept_agent_task, em_apply_to_task, em_approve_submission). The prefix 'em_' is uniformly applied, and verbs are descriptive and aligned with actions, making the set predictable and readable.

Tool Count2/5

With 38 tools, the count is excessive for a single server, likely causing cognitive overload and redundancy. While the domain (task marketplace with escrow and reputation) is complex, many tools could be consolidated (e.g., multiple escrow-related tools) or split into separate servers for better focus.

Completeness5/5

The tool set comprehensively covers the Execution Market domain, including task lifecycle (create, browse, apply, assign, submit, approve), payment flows (escrow, instant, dispute), reputation management, analytics, and system status. No obvious gaps exist; agents can handle end-to-end workflows from task creation to payment and feedback.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedem_publish_task3 fields changed
      • addedInput schema / $defs / GeoMatchMode
        Added value: +{
+  "description": "How strictly a worker's location must match the task location.\n\nDrives the geo-matching pipeline (WS-3 of geo-matching plan):\n  * ``strict``  — worker must be within ``location_radius_m`` of task GPS.\n  * ``city``    — worker's resolved city must match the task's city.\n  * ``region``  — worker's region/state must match.\n  * ``country`` — worker's country must match.\n  * ``any``     — no location matching (default when not set).",
+  "enum": [
+    "strict",
+    "city",
+    "region",
+    "country",
+    "any"
+  ],
+  "title": "GeoMatchMode",
+  "type": "string"
+}
      • addedInput schema / $defs / PublishTaskInput / properties / geo_match_mode
        Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/GeoMatchMode"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Worker/task location matching strictness. 'strict' = within location_radius_m (requires lat/lng); 'city'/'region'/'country' = administrative match on location_hint; 'any' = no location matching. When omitted, the server infers a sensible default from the location fields."
+}
      • addedInput schema / $defs / PublishTaskInput / properties / location_radius_m
        Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Override geofence radius in METERS for geo_match_mode='strict'. Defaults to 500m when strict mode is inferred but this field is omitted. Ignored for non-strict modes.",
+  "title": "Location Radius M"
+}
  2. 2 tool updates
    • Changedem_batch_create_tasks3 fields changed
      • changedInput schema / $defs / EvidenceType / enum
        Previous value: -[
-  "photo",
-  "photo_geo",
-  "video",
-  "document",
-  "receipt",
-  "signature",
-  "notarized",
-  "timestamp_proof",
-  "text_response",
-  "measurement",
-  "screenshot"
-]New value: +[
+  "photo",
+  "photo_geo",
+  "video",
+  "document",
+  "receipt",
+  "signature",
+  "notarized",
+  "timestamp_proof",
+  "text_response",
+  "measurement",
+  "screenshot",
+  "json_response",
+  "api_response",
+  "code_output",
+  "file_artifact",
+  "url_reference",
+  "structured_data",
+  "text_report"
+]
      • changedInput schema / $defs / TaskCategory / description
        Previous value: -"Categories of tasks that humans can execute."New value: +"Categories of tasks that executors can complete."
      • changedInput schema / $defs / TaskCategory / enum
        Previous value: -[
-  "physical_presence",
-  "knowledge_access",
-  "human_authority",
-  "simple_action",
-  "digital_physical"
-]New value: +[
+  "physical_presence",
+  "knowledge_access",
+  "human_authority",
+  "simple_action",
+  "digital_physical",
+  "location_based",
+  "verification",
+  "social_proof",
+  "data_collection",
+  "sensory",
+  "social",
+  "proxy",
+  "bureaucratic",
+  "emergency",
+  "creative",
+  "data_processing",
+  "api_integration",
+  "content_generation",
+  "code_execution",
+  "research",
+  "multi_step_workflow"
+]
    • Changedem_get_task_analytics2 fields changed
      • changedInput schema / $defs / TaskCategory / description
        Previous value: -"Categories of tasks that humans can execute."New value: +"Categories of tasks that executors can complete."
      • changedInput schema / $defs / TaskCategory / enum
        Previous value: -[
-  "physical_presence",
-  "knowledge_access",
-  "human_authority",
-  "simple_action",
-  "digital_physical"
-]New value: +[
+  "physical_presence",
+  "knowledge_access",
+  "human_authority",
+  "simple_action",
+  "digital_physical",
+  "location_based",
+  "verification",
+  "social_proof",
+  "data_collection",
+  "sensory",
+  "social",
+  "proxy",
+  "bureaucratic",
+  "emergency",
+  "creative",
+  "data_processing",
+  "api_integration",
+  "content_generation",
+  "code_execution",
+  "research",
+  "multi_step_workflow"
+]
  3. 1 tool update
    • Changedem_publish_task1 field changed
      • addedInput schema / $defs / PublishTaskInput / properties / gps_required
        Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Whether GPS coordinates are required in evidence. None (default): auto-detect based on category and evidence types. False: explicitly disable GPS check (e.g. for screenshot or digital tasks). True: enforce GPS even for non-physical categories.",
+  "title": "Gps Required"
+}
  4. 38 tool updates
    • First observedem_accept_agent_task
    • First observedem_apply_to_task
    • First observedem_approve_submission
    • First observedem_assign_task
    • First observedem_batch_create_tasks
    • First observedem_browse_agent_tasks
    • First observedem_calculate_fee
    • First observedem_cancel_task
    • First observedem_check_escrow_state
    • First observedem_check_identity
    • First observedem_check_submission
    • First observedem_escrow_authorize
    • First observedem_escrow_charge
    • First observedem_escrow_dispute
    • First observedem_escrow_partial_release
    • First observedem_escrow_recommend_strategy
    • First observedem_escrow_refund
    • First observedem_escrow_release
    • First observedem_escrow_status
    • First observedem_get_arbiter_verdict
    • First observedem_get_fee_structure
    • First observedem_get_my_executions
    • First observedem_get_my_tasks
    • First observedem_get_payment_info
    • First observedem_get_reputation
    • First observedem_get_task
    • First observedem_get_task_analytics
    • First observedem_get_tasks
    • First observedem_publish_task
    • First observedem_rate_agent
    • First observedem_rate_worker
    • First observedem_register_as_executor
    • First observedem_register_identity
    • First observedem_resolve_dispute
    • First observedem_server_status
    • First observedem_submit_agent_work
    • First observedem_submit_work
    • First observedem_withdraw_earnings

Related MCP Connectors

Related MCP Servers

  • x402 Ads MCP

    forgemeshlabs
    A
    license
    A
    quality
    A
    maintenance
    x402 Ads lets AI agents buy and verify ad placements with per-request USDC payments. Agents can discover inventory, submit campaign context, receive structured placement options, and pay through x402 without API keys or accounts. Built for autonomous promotion, attribution, and pay-per-action agent commerce.
    7
    84 npm
    MIT
  • cyberdyne-mcp by Cyberdyne-OS

    cyberdyne-mcpofficial

    Cyberdyne-OS
    A
    license
    A
    quality
    F
    maintenance
    Lets an AI agent hire and pay a verified human: post real-world tasks (voice, observation, judgment) and pay in USDC via a non-custodial x402 auth-capture escrow on Base, budget frozen at deploy. Humans verify their X identity before submitting.
    8
    33 npm
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources