AdCritter for Builders
REMOTE · MCP.ADCRITTER.COM · SCANNED AUG 3
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1336 tokens (~190/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.adcritter.com
claude mcp add --transport http com-adcritter-mcp-dev https://mcp.adcritter.com/mcp/dev
[mcp_servers.com-adcritter-mcp-dev] url = "https://mcp.adcritter.com/mcp/dev"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-adcritter-mcp-dev": {
"type": "remote",
"url": "https://mcp.adcritter.com/mcp/dev",
"enabled": true
}
}
} openclaw mcp add com-adcritter-mcp-dev --url https://mcp.adcritter.com/mcp/dev --transport streamable-http
mcp_servers:
com-adcritter-mcp-dev:
url: "https://mcp.adcritter.com/mcp/dev" {
"mcpServers": {
"com-adcritter-mcp-dev": {
"type": "http",
"url": "https://mcp.adcritter.com/mcp/dev"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.adcritter.com/mcp/dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.adcritter.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 17 Apr 2026 | 17 Oct 2026 | RSA 2048 | SHA256-RSA | 8178262f37569043f75a0ea62e81639 |
| SANs: mcp.adcritter.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
DNSSEC insecure
Validation of mcp.adcritter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| adcritter.com. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.adcritter.com/mcp/dev | Verified | 200 | |
| http (plaintext) | http://mcp.adcritter.com/mcp/dev | HTTPS enforced | 301 | https://mcp.adcritter.com/mcp/dev |
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.
adcritter_build_app ~81
Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adcritter_get_api_reference ~194
Returns the REST API contract for an AdCritter entity. Without an action parameter, returns a summary with available action names - use this to discover what you can do. With an action parameter (e.g., 'create', 'list', 'get'), returns the full details for that action: route, HTTP method, request schema, response schema, error codes, and constraints. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, canva, domain, facebook, geo, googleads, media-asset, me, plan, report, segment, settings, targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | Optional specific action to drill into (e.g., 'create', 'list', 'get', 'update', 'delete'). Omit to see all available actions. |
| entity | string | yes | The entity to look up (e.g., 'campaign', 'ad', 'report') |
No output schema declared.
No examples provided.
adcritter_get_design_guide ~256
Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | The entity to look up (e.g., 'campaign', 'report', 'authentication') |
| guidance | string | — | Optional guidance level. Values: 'full' (facts + patterns + prescription, the default), 'patterns' (facts + softened patterns, for capable callers who want structure without exact prescription), 'fac… |
No output schema declared.
No examples provided.
adcritter_get_platform_overview ~134
Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adcritter_get_usage_guide ~121
Returns the conceptual model and workflow guidance for an AdCritter entity - what it is, how it relates to other entities, and the intended workflow for using it. Includes exhaustive workflow sequencing and prescriptive rules so generated apps call the API correctly. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, domain, geo, media-asset, me, plan, report, segment, settings, targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | The entity to look up (e.g., 'campaign', 'geo', 'plan') |
No output schema declared.
No examples provided.
adcritter_guidance ~108
Returns detailed building instructions for a specific feature area of an AdCritter application. Each guide describes what to build, how users should experience it, and includes all API endpoints with request/response shapes so you never have to guess the API contract. Call adcritter_build_app first to see available feature guides and their keys.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The feature guide key from the adcritter_build_app catalog (e.g., 'auth', 'dashboard', 'campaign-create') |
No output schema declared.
No examples provided.
adcritter_health ~25
Returns server health status and version information for the AdCritter MCP server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.