AdMakeAI
REMOTE · ADMAKEAI.COM · SCANNED AUG 22
Generate ad images and UGC videos, research competitor ads, and manage Meta ad campaigns.
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the AdMakeAI MCP server?
AdMakeAI is a hosted endpoint at https://admakeai.com/api/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 · admakeai.com
claude mcp add --transport http com-admakeai-admakeai 'https://admakeai.com/api/mcp'
{
"mcpServers": {
"com-admakeai-admakeai": {
"url": "https://admakeai.com/api/mcp"
}
}
} {
"servers": {
"com-admakeai-admakeai": {
"type": "http",
"url": "https://admakeai.com/api/mcp"
}
}
} [mcp_servers.com-admakeai-admakeai] url = "https://admakeai.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-admakeai-admakeai": {
"type": "remote",
"url": "https://admakeai.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-admakeai-admakeai --url 'https://admakeai.com/api/mcp' --transport streamable-http
mcp_servers:
com-admakeai-admakeai:
url: "https://admakeai.com/api/mcp" {
"McpServers": {
"com-admakeai-admakeai": {
"Transport": "http",
"Url": "https://admakeai.com/api/mcp"
}
}
} assistant mcp add com-admakeai-admakeai -t streamable-http -u 'https://admakeai.com/api/mcp'
{
"mcpServers": {
"com-admakeai-admakeai": {
"type": "http",
"url": "https://admakeai.com/api/mcp"
}
}
} 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.
- 11 Aug 26 37
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 22 Aug 2026 · Probed https://admakeai.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=admakeai.com | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | bf353db68d9425a313d045eca5475f79 |
| SANs: admakeai.com, *.admakeai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of admakeai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| admakeai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="admakeai", error="invalid_request", error_description="Missing credentials. Send an API key as x-api-key: <key>, or connect over OAuth and send Authorization: Bearer <token>.", resource_metadata="https://admakeai.com/.well-known/oauth-protected-resource/api/mcp", scope="mcp:read mcp:write mcp:publish"
Bearer realm="admakeai", error="invalid_request", error_description="Missing credentials. Send an API key as x-api-key: <key>, or connect over OAuth and send Authorization: Bearer <token>.", resource_metadata="https://admakeai.com/.well-known/oauth-protected-resource/api/mcp", scope="mcp:read mcp:write mcp:publish"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="admakeai", error="invalid_request", error_description="Missing credentials. Send an API key as x-api-key: <key>, or connect over OAuth and send Authorization: Bearer <token>.", resource_metadata="https://admakeai.com/.well-known/oauth-protected-resource/api/mcp", scope="mcp:read mcp:write mcp:publish" |
Protected resource metadata
| Document | https://admakeai.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://admakeai.com/api/mcp |
| Authorisation server | https://admakeai.com |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://admakeai.com/api/mcp | Auth required | 401 | |
| http (plaintext) | http://admakeai.com/api/mcp | HTTPS enforced | 301 | https://admakeai.com/api/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.
No tool schema has been captured from this endpoint yet.
What is the AdMakeAI MCP server?
AdMakeAI is an MCP server listed in the public MCP registry as com.admakeai/admakeai. Generate ad images and UGC videos, research competitor ads, and manage Meta ad campaigns. This page covers its hosted endpoint (https://admakeai.com/api/mcp).
Is the AdMakeAI MCP server safe to use?
AdMakeAI scores 37 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.
Does the AdMakeAI MCP server require authentication?
Yes. AdMakeAI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AdMakeAI MCP server still maintained?
AdMakeAI is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.