io.github.jshorwitz/synter-ads
REMOTE · MCP.SYNTERMEDIA.AI · 2 COMPONENTS · SCANNED SEP 21
Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.
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 → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 25001 tokens (~119/item across 209 items; 209 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 Management95
- Stability check failed: schema churn in the 30 days we've observed: 7 tool removals, 1 breaking changes, 0 auth/transport breaks, 60 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 12 of 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_gaql_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 210 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jshorwitz/synter-ads MCP server?
io.github.jshorwitz/synter-ads is a hosted endpoint at https://mcp.syntermedia.ai/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.syntermedia.ai
claude mcp add --transport http jshorwitz-synter-ads 'https://mcp.syntermedia.ai/mcp/'
{
"mcpServers": {
"jshorwitz-synter-ads": {
"url": "https://mcp.syntermedia.ai/mcp/"
}
}
} {
"servers": {
"jshorwitz-synter-ads": {
"type": "http",
"url": "https://mcp.syntermedia.ai/mcp/"
}
}
} [mcp_servers.jshorwitz-synter-ads] url = "https://mcp.syntermedia.ai/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jshorwitz-synter-ads": {
"type": "remote",
"url": "https://mcp.syntermedia.ai/mcp/",
"enabled": true
}
}
} openclaw mcp add jshorwitz-synter-ads --url 'https://mcp.syntermedia.ai/mcp/' --transport streamable-http
mcp_servers:
jshorwitz-synter-ads:
url: "https://mcp.syntermedia.ai/mcp/" {
"McpServers": {
"jshorwitz-synter-ads": {
"Transport": "http",
"Url": "https://mcp.syntermedia.ai/mcp/"
}
}
} assistant mcp add jshorwitz-synter-ads -t streamable-http -u 'https://mcp.syntermedia.ai/mcp/'
{
"mcpServers": {
"jshorwitz-synter-ads": {
"type": "http",
"url": "https://mcp.syntermedia.ai/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.
- 21 Sept 26 +6
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 −6
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 21 Sept 2026 · Probed https://mcp.syntermedia.ai/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.syntermedia.ai | CN=YR1,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 5dbc93cd9d736000581fea3bd7546081504 |
| SANs: mcp.syntermedia.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.syntermedia.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| syntermedia.ai. | 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 tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.syntermedia.ai/.well-known/oauth-protected-resource", scope="tools:read tools:write"
Bearer resource_metadata="https://mcp.syntermedia.ai/.well-known/oauth-protected-resource", scope="tools:read tools:write"Protected resource metadata
| Document | https://mcp.syntermedia.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.syntermedia.ai |
| Authorisation server | https://mcp.syntermedia.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.syntermedia.ai/mcp/ | Verified | 200 | |
| http (plaintext) | http://mcp.syntermedia.ai/mcp/ | HTTPS enforced | 301 | https://mcp.syntermedia.ai/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 →
update_landing_page_tracking Update Landing Page Tracking ~147
Set workspace-owned landing-page pixels, GA4, and the Google Ads conversion label, and wire a Fillout embed so form submits count as campaign conversions using the existing workspace integrations. Free edit of a page you own. Returns google_send_to plus a Fillout webhook URL. [effect=write; scope=landing_pages:write]
| Name | Type | Req | Description |
|---|---|---|---|
| fillout_form_id | – | – | – |
| ga4_measurement_id | – | – | – |
| google_conversion_label | – | – | – |
| google_pixel_id | – | – | – |
| linkedin_pixel_id | – | – | – |
| meta_pixel_id | – | – | – |
| reddit_pixel_id | – | – | – |
| rotate_webhook_token | boolean | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
update_verified_page_replica Update Verified Page Replica ~52
Get status, verify, or revoke source ownership for a verified page replica. [effect=write; scope=landing_pages:write]
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
upload_creative Upload Creative ~119
Upload a generated creative asset to an ad platform and attach it to a campaign (5 credits) [effect=publish; scope=creative:publish; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| ad_group_id | – | – | – |
| asset_type | string | – | – |
| asset_url | string | yes | – |
| campaign_id | string | yes | – |
| description | – | – | – |
| form_id | – | – | – |
| headline | – | – | – |
| landing_url | – | – | – |
| name | – | – | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
upload_landing_page_html Upload Landing Page HTML ~138
Upload raw HTML as a new landing-page draft (no AI generation). Use to import an exported .html file or hand-written markup (embedded forms, Cal.com embeds, thank-you pages all supported). Then publish_landing_page and attach it to an ad campaign. Creating a new hosted page costs 135 credits (same as create_landing_page); re-uploading to a slug you already own is a free edit. [effect=publish; scope=landing_pages:publish; requires=campaignPublishing; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| html_content | string | yes | – |
| slug | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
upsert_plan_entity Upsert Plan Entity ~121
Add or update an entity (campaign, ad, tweet, go_link, etc.) within a campaign plan. [effect=write; scope=campaigns:plan; externalMutation=true]
| Name | Type | Req | Description |
|---|---|---|---|
| desired_state | string | – | – |
| entity_type | string | yes | – |
| logical_key | string | yes | – |
| metadata_json | – | – | – |
| parent_logical_key | – | – | – |
| plan_id | string | yes | – |
| platform | string | yes | – |
| provider_account_id | – | – | – |
| remote_id | – | – | – |
| remote_ref_json | – | – | – |
No output schema declared.
No examples provided.
validate_organic_post Validate Organic Post ~76
Run a non-publishing provider capability preflight for the exact immutable revision, tenant, connection, provider config, LinkedIn member/company destination, token, and effective scopes. [effect=write; scope=social:write; requires=campaignPublishing]
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | – |
| revision_hash | string | yes | – |
No output schema declared.
No examples provided.
verify_custom_domain Verify Custom Domain ~47
Check if DNS is configured for a landing page's custom domain. Free — no credits charged. [effect=read; scope=landing_pages:read]
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
verify_pixel_ownership Verify Pixel Ownership ~82
Cross-validate that the pixel/tag IDs on a landing page belong to the connected ad account. Detects wrong-pixel installs, domain registration gaps, and CAPI mismatches. Free — no credits. [effect=read; scope=tracking:read]
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | – | – | – |
| platform | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
verify_platform_accounts Verify Platform Accounts ~87
Verify which ad account each platform's pull tools would use by default, with recent activity per connected account. Flags when the default account is dormant while a sibling account has spend (free). Call this before pull_*_performance when a platform has multiple accounts or returns suspicious zeros. [effect=read; scope=connections:read]
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| platform | – | – | – |
No output schema declared.
No examples provided.
What is the io.github.jshorwitz/synter-ads MCP server?
io.github.jshorwitz/synter-ads is an MCP server listed in the public MCP registry as io.github.jshorwitz/synter-ads. Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI. This page covers its hosted endpoint (https://mcp.syntermedia.ai/mcp/).
Is the io.github.jshorwitz/synter-ads MCP server safe to use?
io.github.jshorwitz/synter-ads scores 85 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 io.github.jshorwitz/synter-ads MCP server expose?
io.github.jshorwitz/synter-ads exposes 209 tools: get_organic_publishing_readiness, draft_organic_post, validate_organic_post, approve_organic_post, schedule_organic_post, and 204 more. Their descriptions and schemas cost roughly 20,927 tokens of context every time the server is loaded.
Does the io.github.jshorwitz/synter-ads MCP server require authentication?
Yes. io.github.jshorwitz/synter-ads 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 io.github.jshorwitz/synter-ads MCP server still maintained?
io.github.jshorwitz/synter-ads is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.