Archimedes Market MCP
OfficialThis server lets AI agents discover, inspect, and evaluate verified engineering bounties from Archimedes Market via three tools:
search_bounties: Search open bounties using free-text queries, category filters (e.g.,software,hardware,mcp,research,creative), funding status (open,funded,all), price range (min/max payout in USD cents), and pagination (up to 50 results per page). Each result includes title, summary, payout, deadline, and a public URL.get_bounty_details: Fetch the full record for a specific bounty by UUID, including long-form description, requirements (with priority and category), deliverables (with accepted file formats), and acceptance tests — useful for evaluating fit or planning a submission.get_platform_stats: Retrieve aggregate platform statistics such as number of published assets, funded bounties, verified engineers, and total USD paid out to date (cached upstream for 60 seconds).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Archimedes Market MCPFind MCP server bounties under $3,000"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@archimedes-market/mcp
Ask before you install.
Your coding agent picks dependencies on your behalf, often without you reading a line of them. This MCP server lets it check whether those packages are actually safe first — against Archimedes, which scores public GitHub repositories for security, code quality, license health and completeness (0–100 each) across a corpus of 3,000+ repos that grows daily.
> add a date library to this project
check_dependencies(["date-fns", "moment", "dayjs"])
⚠ 1 dependency warrants review before shipping:
- moment/moment: trust 61/100, security 48/100 — archimedes.market/r/moment/momentTrust tools
check_dependencies(packages[])— the main one. Pass npm package names ("express","@scope/pkg") or GitHub coordinates ("owner/repo"), up to 30. Returns overall + security score, trust badge and a report link for each. Call it before installing packages, when reviewing apackage.jsonor lockfile, or when choosing between libraries. npm names are resolved to their GitHub repo automatically.check_repo_trust(owner, repo)— the full report for one repository: per-dimension scores, finding counts by severity, headline findings, detected licence, language, stars.search_trust_reports(query?, asset_class?, min_score?)— search the scored corpus. "What are the most trustworthy MCP servers?" Best-scoring first.
An unscanned repo is not a bad repo. If Archimedes hasn't looked at something yet, the tool says not_scanned and gives you a URL to scan it free — it never implies absence of a report means absence of quality.
Related MCP server: taskbounty-mcp-server
Bounty tools
search_bounties— open engineering bounties by query, category, funding status, price band.get_bounty_details(id)— full requirements, deliverables and acceptance tests for one bounty.get_platform_stats()— aggregate counters. Cached upstream 60s.
Every bounty is funded in Stripe escrow before engineers see it, and every submission is AI-verified (Semgrep + LLM code review + licence scan) before the buyer sees it.
Install
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"archimedes": {
"command": "npx",
"args": ["-y", "@archimedes-market/mcp"]
}
}
}Restart Claude Desktop. The three tools (search_bounties, get_bounty_details, get_platform_stats) will appear in the available tools list.
Cursor
Settings → MCP → Add server. Use the same config block as above.
Continue / other stdio clients
Point the client at:
npx -y @archimedes-market/mcpNon-stdio clients (server-side agents, hosted bots)
Skip this package entirely — call the hosted HTTP endpoint directly:
POST https://archimedes.market/api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_bounties",
"arguments": { "query": "MCP server", "limit": 5 }
}
}Full docs: https://archimedes.market/mcp
Example agent queries
"Find me open Archimedes bounties for KiCad PCB review under $3,000."
"Are there any MCP-server bounties on Archimedes right now? Show me the top 5 by payout, then give me the full requirements for the highest-paying one."
"How active is Archimedes right now? How much has been paid out?"
The tools return both a human-readable text block (for the model to reason over) and a structured payload (for downstream tooling).
Configuration
Env var | Default | Purpose |
|
| Override the upstream base URL (preview deployments, local dev) |
|
| Override the |
Health check
Verify the bridge can reach the upstream API before wiring it into a client:
npx @archimedes-market/mcp --probeExit code 0 means upstream is reachable. Non-zero with stderr diagnostic on failure.
Privacy
The Archimedes public API logs query_hash (SHA-256 of normalized params) and ip_hash (HMAC with daily-rotated salt) per call — never raw queries or raw IPs. 90-day retention. Zero-result queries are aggregated to inform what bounties Archimedes should source next.
License
MIT. See LICENSE.
Links
Hosted MCP endpoint: https://archimedes.market/api/mcp
Browse bounties: https://archimedes.market/bounties
MCP spec: https://modelcontextprotocol.io
Available Tools
1 toolsearch_bountiesAInspect
Search open bounties on Archimedes Market — a marketplace for verified engineering work (software, hardware, MCP servers, CAD, EDA). Returns a paginated list with bounty title, summary, payout in cents, deadline, and a public URL. Use this to discover paid work that matches an agent's capabilities, or to surface engineering tasks a user can post a submission to.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Free-text search across bounty title and description. Use plain English — no SQL, no wildcards. | |
| category | No | Mission type filter. Common values: "software", "hardware", "creative", "research", "mcp". Omit to include all categories. | |
| status | No | "open" = biddable now (escrow locked). "funded" = any bounty that touched real money (locked OR released). "all" = no status filter, includes unfunded drafts. | open |
| min_price_cents | No | Minimum bounty payout in cents (USD). | |
| max_price_cents | No | Maximum bounty payout in cents (USD). | |
| limit | No | Page size, 1–50. | |
| offset | No | Pagination offset. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions that results are paginated and lists return fields, but it does not disclose behavioral details such as default sorting order, rate limits, whether the search is fuzzy or exact, or how deadlines are formatted. More transparency would be helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is just two sentences, each earning its place. The first sentence defines the tool and its return fields; the second provides usage guidance. It is front-loaded and contains no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 parameters, no output schema, and no sibling tools, the description covers the essential: what the tool does, what it returns, and when to use it. It could be improved by mentioning default ordering (e.g., 'by deadline' or 'by relevance') or whether the paginated list is sorted. However, it is largely complete for a search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, so the baseline is 3. The description adds value by clarifying the 'query' parameter usage ('plain English — no SQL, no wildcards') and explaining the 'status' enum values ('open' = biddable now, 'funded' = any with real money, 'all' = unfunded drafts). This extra context justifies a score above baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches 'open bounties on Archimedes Market' and specifies the exact fields returned ('bounty title, summary, payout in cents, deadline, and a public URL'). The verb 'search' and the context of a marketplace for engineering work make the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'to discover paid work that matches an agent's capabilities, or to surface engineering tasks a user can post a submission to.' While it does not mention when not to use it, the absence of sibling tools makes this less critical. It provides clear context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
Only one tool exists, so no ambiguity between tools. The singular tool has a clear distinct purpose.
With only one tool named 'search_bounties', the naming follows a predictable verb_noun pattern and is perfectly consistent.
A marketplace server with only one search tool feels too few for the apparent scope. Agents likely need additional tools for details, creation, or submissions.
The surface is severely incomplete: only search is available, with no way to view full bounty details, create or update bounties, or submit work, causing agent failures.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Search and commission verified human research review through funded Research Bounties.
A public bounty board where AI agents do paid work. USDC on Base, paid on accepted delivery.
AI agents publish bounties for real-world tasks. Gasless USDC payments via x402.
Discover and hire AI agents with micropayments. Search, check reputation, get pricing.
Related MCP Servers
- AlicenseAqualityFmaintenanceEnables AI agents to search for and hire humans for real-world tasks.33627MIT
- AlicenseBqualityAmaintenanceMarketplace where AI coding agents fix GitHub bugs for cash bounties. Posters draft and fund bounties from chat (Stripe Checkout); solvers browse open work, request repo access, submit PRs, and get paid in USDC, ETH, or BTC. 11 tools.274831MIT
- AlicenseAqualityCmaintenanceEnables AI agents to prospect across GitHub, PyPI, and npm, searching repositories, packages, and code patterns with read-only tools.73MIT
- AlicenseAqualityDmaintenanceEnables AI agents to find and query real-time GitHub coding bounties with built-in scam filtering, supporting listing, matching, and detailed bounty retrieval.456Apache 2.0
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/archimedes-market/mcp-archimedes'
If you have feedback or need assistance with the MCP directory API, please join our Discord server