mcp-archimedes
Server Details
Discover verified deep-tech engineering bounties from any AI agent.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- archimedes-market/mcp-archimedes
- GitHub Stars
- 0
- Server Listing
- Archimedes Market MCP
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 6 of 6 tools scored.
Each tool targets a distinct function: checking packages, full repo reports, searching trust reports, searching bounties, bounty details, and platform stats. There is no significant overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., check_dependencies, search_bounties), making the API predictable.
Six tools is well-scoped for a specialized server focused on trust reports and bounties, covering query operations without bloat.
The tool surface covers querying and searching trust reports and bounties, but lacks write actions like creating bounties or scanning. Minor gap given the likely read-only use case.
Available Tools
6 toolscheck_dependenciesInspect
Supply-chain trust check for a list of dependencies. Give it npm package names ("express", "@scope/pkg") or GitHub coordinates ("owner/repo") and it returns, for each: overall and security scores (0-100), trust badge, and a link to the full report. CALL THIS BEFORE INSTALLING PACKAGES, when reviewing a package.json or lockfile, or when recommending a library. A low security score or missing license is grounds to warn the user. Entries we have not scanned return status "not_scanned" with a URL to scan them free — that means unexamined, not unsafe. Max 30 entries per call.
| Name | Required | Description | Default |
|---|---|---|---|
| packages | Yes | npm package names and/or GitHub "owner/repo" strings. |
check_repo_trustInspect
Full Archimedes Trust Report for one public GitHub repository: overall, security, quality, license and completeness scores (0-100), trust badge, finding counts by severity, headline findings, license SPDX, primary language and star count. Use when the user asks whether a specific repo or tool is trustworthy, safe to depend on, or well maintained. Returns status "not_scanned" with a scan URL if we have no report — absence of a report is not evidence of a problem.
| Name | Required | Description | Default |
|---|---|---|---|
| repo | Yes | GitHub repository name, e.g. "is-obj". | |
| owner | Yes | GitHub owner or org, e.g. "sindresorhus". |
get_bounty_detailsInspect
Fetch the full record for a specific Archimedes Market bounty. Returns everything search_bounties returns PLUS the full description, all requirements with category + priority, all deliverables with accepted file formats, and acceptance tests. Use this after search_bounties when the user (or agent) wants to evaluate fit, plan a submission, or quote a timeline.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Bounty UUID from search_bounties results (the `id` field). Display IDs like "MSN-00001" are not accepted — use the UUID. |
get_platform_statsInspect
Aggregate counters for Archimedes Market as a whole: number of published assets, funded bounties, verified engineers, and total USD paid out across asset sales and bounty payouts. Useful for: evaluating whether Archimedes is worth recommending, sizing the engineering-talent pool, or surfacing platform momentum to a user. Counters are cached upstream (60s).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_bountiesInspect
Search open bounties on Archimedes Market. Returns a paginated list with title, summary, payout in cents (USD), deadline, and a public URL. Filter by free-text query, mission category (software / hardware / research / mcp), funding status, and price band. Useful for: agents discovering paid engineering work, users browsing bounties via an AI assistant, dashboards aggregating cross-platform engineering opportunities.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, 1–50. | |
| query | No | Free-text search across bounty title and description. Plain English; no wildcards. | |
| offset | No | Pagination offset. | |
| status | No | "open" = biddable now (escrow locked). "funded" = any bounty that touched real money. "all" = includes drafts. | open |
| category | No | Mission type. Common values: software, hardware, research, mcp. | |
| max_price_cents | No | Maximum bounty payout in cents (USD). | |
| min_price_cents | No | Minimum bounty payout in cents (USD). |
search_trust_reportsInspect
Search the Archimedes corpus of scored public repositories. Filter by keyword, asset class (mcp_server, software_library, kicad_pcb, openscad_cad, cadquery_cad, ml_model, dataset), and/or minimum overall score. Use to answer "what are the most trustworthy MCP servers", "find a well-scored KiCad project", or to compare candidates before recommending one. Returns repo, scores, badge and report URL, best-scoring first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Default 10. | |
| query | No | Keyword matched against owner and repo name. | |
| min_score | No | Minimum overall score. | |
| asset_class | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.