# io.github.archimedes-market/mcp-archimedes (remote · archimedes.market)

Discover verified deep-tech engineering bounties from any AI agent.

- Trust score: 63/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `archimedes.market`: 63/100 (this document), [markdown](https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp.md), [page](https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp)
- npm · `@archimedes-market/mcp`: 69/100, [markdown](https://verifymcp.io/servers/archimedes-market-mcp-archimedes/archimedes-market-mcp.md), [page](https://verifymcp.io/servers/archimedes-market-mcp-archimedes/archimedes-market-mcp)

## Channel facts

- Endpoint: `https://archimedes.market/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1163 tokens (~193/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http archimedes-market-mcp-archimedes https://archimedes.market/api/mcp
```

### Codex

```toml
[mcp_servers.archimedes-market-mcp-archimedes]
url = "https://archimedes.market/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "archimedes-market-mcp-archimedes": {
      "type": "remote",
      "url": "https://archimedes.market/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add archimedes-market-mcp-archimedes --url https://archimedes.market/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  archimedes-market-mcp-archimedes:
    url: "https://archimedes.market/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "archimedes-market-mcp-archimedes": {
      "type": "http",
      "url": "https://archimedes.market/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (6)

### `check_dependencies` (~159 tokens)

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.

Input parameters:

- `packages` (array, required): npm package names and/or GitHub "owner/repo" strings.

### `check_repo_trust` (~150 tokens)

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.

Input parameters:

- `owner` (string, required): GitHub owner or org, e.g. "sindresorhus".
- `repo` (string, required): GitHub repository name, e.g. "is-obj".

### `search_trust_reports` (~150 tokens)

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.

Input parameters:

- `asset_class` (string)
- `limit` (number): Default 10.
- `min_score` (number): Minimum overall score.
- `query` (string): Keyword matched against owner and repo name.

### `search_bounties` (~234 tokens)

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.

Input parameters:

- `category` (string): Mission type. Common values: software, hardware, research, mcp.
- `limit` (integer): Page size, 1–50.
- `max_price_cents` (integer): Maximum bounty payout in cents (USD).
- `min_price_cents` (integer): Minimum bounty payout in cents (USD).
- `offset` (integer): Pagination offset.
- `query` (string): Free-text search across bounty title and description. Plain English; no wildcards.
- `status` (string): "open" = biddable now (escrow locked). "funded" = any bounty that touched real money. "all" = includes drafts.

### `get_bounty_details` (~122 tokens)

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.

Input parameters:

- `id` (string, required): Bounty UUID from search_bounties results (the `id` field). Display IDs like "MSN-00001" are not accepted — use the UUID.

### `get_platform_stats` (~82 tokens)

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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://archimedes.market/api/mcp
- Repository: https://github.com/archimedes-market/mcp-archimedes
- Changelog RSS feed: https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/archimedes-market-mcp-archimedes/api-mcp