Context Studios MCP
REMOTE · MCP.CONTEXTSTUDIOS.AI
AI agency API: free tools for glossary, comparisons, blog, guides, estimates and consulting
Available components
Last scanned (1 hour ago)
Scores higher than 96% of remote servers
Reachable. Last reached 17 Oct 2026.
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4984 tokens (~101/item across 49 items; 46 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability check failed: schema churn in the 29 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 19 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 46 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 96 to 89.
- 2 Oct 26 0
- Tool “get_services” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- Schema quality: good → excellent functional
- New tool “find_local_ai_recipes” functional
- New tool “get_local_ai_creator” functional
- New tool “get_local_ai_methodology” functional
- New tool “get_local_ai_quality” functional
- New tool “get_local_ai_recipe” functional
- New tool “list_local_ai_creators” functional
- New tool “list_local_ai_hardware” functional
- New tool “list_local_ai_recipes” functional
- “get_services” added an optional parameter “cluster” cosmetic
- “get_services” added an optional parameter “format” cosmetic
- “get_services” dropped the optional parameter “category” cosmetic
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 2.1.0 ▼ security
- Tool “get_pricing” was removed ▼ security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- The server now declares the “completions” capability functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New tool “get_company_type” functional
- New tool “get_faq” functional
- New tool “get_industry” functional
- New tool “get_pricing_model” functional
- New tool “get_role” functional
- New tool “get_use_case” functional
- New tool “get_workshops” functional
- New tool “list_company_types” functional
- New tool “list_industries” functional
- New tool “list_roles” functional
- New tool “list_use_cases” functional
- “fetch” reworded the description of “id” cosmetic
- “get_company_info” reworded the description of “sections” cosmetic
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 +57
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 27 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 16 Sept 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://mcp.contextstudios.ai/api/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.contextstudios.ai | CN=YR1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 66cd9ebb738e40bbfe565aaa2d9cf966ee6 |
| SANs: mcp.contextstudios.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.contextstudios.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| contextstudios.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.contextstudios.ai/api/public/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.contextstudios.ai/api/public/mcp | HTTPS enforced | 308 | https://mcp.contextstudios.ai/api/public/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_pages Search Pages ~112
Full-text search across all published CMS pages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results to return. |
| locale | string | – | Preferred content locale. Supported values are de, en, fr, and it. Some source catalogs may fall back to de or en. |
| query | string | yes | Search query or keyword phrase. Use the user's natural-language topic. |
| responseFormat | string | – | Response shape. Use v2 for agent-friendly {success,data,meta,error}; legacy remains available for older clients. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of returned records for list and search tools. |
| data | – | – | Structured result payload. Present for responseFormat='v2' tools. |
| error | string | – | Human-readable error message when success is false. |
| meta | – | – | Result metadata such as count, locale fallback, cache scope, or response format. |
| success | boolean | – | Whether the tool call completed successfully. |
No examples provided.
How do I install the Context Studios MCP server?
Context Studios MCP is a hosted endpoint at https://mcp.contextstudios.ai/api/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.contextstudios.ai
claude mcp add --transport http ai-contextstudios-mcp 'https://mcp.contextstudios.ai/api/public/mcp'
What is the Context Studios MCP server?
Context Studios MCP is listed in the public MCP registry as ai.contextstudios/mcp. AI agency API: free tools for glossary, comparisons, blog, guides, estimates and consulting. This page covers its hosted endpoint (https://mcp.contextstudios.ai/api/public/mcp).
Is the Context Studios MCP server safe to use?
Context Studios MCP scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Context Studios MCP server expose?
Context Studios MCP exposes 46 tools: ai_project_estimator, blog_explorer, fetch, find_local_ai_recipes, get_blog_posts, and 41 more. Their descriptions and schemas cost roughly 4,875 tokens of context every time the server is loaded.
Does the Context Studios MCP server require authentication?
No. We connected to Context Studios MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Context Studios MCP server still maintained?
Context Studios MCP is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.