Inspo by Context.dev (remote)

65/100

Capped at 65: vendor-hosted, source not published. The tests add up to 65.

Last tested 2026-11-10 (Fresh: tested within 30 days) Working (tool call tested 2026-11-10) No key needed for the tools we called

Advisories: not checked (remote-only)

Security review: not tested

Test points add up to 65; the score is capped at 65 (vendor-hosted, source not published). Not a quality or security rating. Capped listings are not promoted in our rankings or on the homepage. Why scores are capped

Test points before the cap (65/100)

  • Install20/20
  • Handshake30/30
  • Maintenance0/25
  • Docs15/15
  • License0/10
Two different Inspo products. This listing is Context.dev's hosted remote at inspo.context.dev (one tool, search_designs). It is not the npm package inspo-mcp. See Inspo MCP for Nutlope/inspo's local stdio server.

Vendor-hosted
Tested Inspo by Context.dev at https://inspo.context.dev/mcp (server inspo 1.0.0). Initialize and tools/list over Streamable HTTP succeeded with no credentials and listed 1 tool (search_designs). Real call (no LLM, no credentials): search_designs {brief:'minimal dark SaaS landing page for a developer tool', count:3} returned real-website design references. No public source repository and no dated vendor changelog, so the vendor-hosted rule applies (license 0, maintenance 0, 65 cap; not source-audited). Distinct from the listed npm package inspo-mcp (Nutlope/inspo). Product page https://inspo.context.dev/ states the endpoint and client setup. Evidence: live endpoint probe, Nov 10, 2026 and live endpoint probe, Nov 10, 2026.
Tool-call test (2026-11-10, direct MCP stdio client, no LLM): pass. 1 of 1 call passed anonymously. Evidence: live endpoint probe, Nov 10, 2026.
Context.dev-hosted endpoint (server inspo 1.0.0). Initialize, tools/list (1 tool) and search_designs worked with no account. No public source repository and no dated vendor changelog, so license scores 0, maintenance scores 0, and the vendor-hosted 65 cap applies (Our review, Nov 9, 2026). Distinct from Inspo MCP (official) / inspo-mcp.
Sources: https://inspo.context.dev/

Transport (tested 2026-11-10): Streamable HTTP

Token cost (estimate): approx. 221 tokens, cl100k estimate (1 tool, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 1 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • search_designs — read

remote handshake listed tools without credentials; no recorded key or OAuth

Score 65/100 · Tools 1 · Token cost approx. 221 tokens · Compare · Last tested 2026-11-10 · Server version 1.0.0 · Remote endpoint https://inspo.context.dev/mcp (streamable-http)

Summary: Inspo by Context.dev (remote) completed an MCP handshake without credentials and exposed 1 tools.

Evidence summary

Handshake
pass
Tools listed
1
Context cost
approx. 221 tokens, cl100k estimate (1 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
Login
No key needed for the tools we called
Tested
2026-11-10

Test results

TestResultPointsEvidence
installpass20Endpoint https://inspo.context.dev/mcp reachable over streamable-http (HTTP 200) in 0.8s; no install step for remote servers.
handshakepass30MCP initialize (protocol 2025-06-18, server inspo 1.0.0) + tools/list over streamable-http succeeded with no credentials; 1 tools listed in 0.8s. Tool calls may still need a key.
maintenancefail0Vendor-hosted rule: no dated vendor changelog or release notes found.
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://inspo.context.dev/).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Token cost (estimate): approx. 221 tokens, cl100k estimate for 1 tools · about 3% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-10

  • We connected to the vendor's hosted endpoint with no credentials and asked for its tool list: it listed 1 tool (Method details: MCP initialize then tools/list)
  • Auth response: none. The endpoint answered without any login
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: no dated vendor changelog or release note found (a registry entry alone does not score) (0/25)
  • License: a hosted service has no license to cite (0/10)
  • Token cost (estimate)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Unchanged since the previous snapshot (latest 2026-11-11).

Snapshot hash (fingerprint of the tool list)

dda216200a70: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "inspo-context-remote",
  "version": null,
  "registry": "remote",
  "status": "working",
  "tested": "2026-11-10",
  "tools_count": 1,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://inspo.context.dev/mcp reachable over streamable-http (HTTP 200) in 0.8s; no install step for remote servers."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` (protocol 2025-06-18, server inspo 1.0.0) + `tools/list` over streamable-http succeeded with no credentials; 1 tools listed in 0.8s. Tool calls may still need a key."
    ],
    "maintenance": [
      "fail",
      0,
      "Vendor-hosted rule: no dated vendor changelog or release notes found."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://inspo.context.dev/)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://inspo.context.dev/mcp

Tools listed

search_designs

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "inspo-by-context-dev-remote": {
      "type": "http",
      "url": "https://inspo.context.dev/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. No install step: it is a remote server at https://inspo.context.dev/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (1 in our test).
{
  "mcpServers": {
    "inspo-by-context-dev-remote": {
      "type": "http",
      "url": "https://inspo.context.dev/mcp"
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is Inspo by Context.dev deprecated?

No. inspo-context-remote was not deprecated or archived when we last tested it on 2026-11-10.

What replaces Inspo by Context.dev?

Nothing; Inspo by Context.dev (remote) is not deprecated as of 2026-11-10.

Does Inspo by Context.dev need an API key?

No. It completed an MCP handshake with no credentials and listed 1 tools.

Embed the badge

TestedMCP: 65/100, tested 2026-11-10

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue