Socialapi MCP Server

mcp-socialapi npm v1.2.0

Published by socialapi-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for SocialAPI — manage social media comments, DMs, reviews, and mentions across platforms

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: social_api_get_creator_info → social_api_list_keys → social_api_create_export. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow social_api_get_creator_info → social_api_list_keys → social_api_create_export

medium Unconstrained URL/host parameter "url" on "social_api_create_webhook"MTC-CAP-007

Tool "social_api_create_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool social_api_create_webhook · inputSchema.properties.url

medium Unconstrained URL/host parameter "url" on "social_api_update_webhook"MTC-CAP-007

Tool "social_api_update_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool social_api_update_webhook · inputSchema.properties.url

Tools 76

Each tool and what it can reach — statically extracted from the published source.

  • social_api_get_exportingests untrusted inputnetwork egress
  • social_api_create_exportnetwork egress
  • social_api_create_webhooknetwork egress
  • social_api_delete_menetwork egress
  • social_api_delete_webhooknetwork egress
  • social_api_get_creator_infoingests untrusted input
  • social_api_get_export_videosnetwork egress
  • social_api_get_media_upload_urlnetwork egress
  • social_api_get_post_metricsingests untrusted input
  • social_api_get_webhooknetwork egress
Show 66 more tools ↓
  • social_api_get_webhook_deliverynetwork egress
  • social_api_list_eventsnetwork egress
  • social_api_list_inbox_postsingests untrusted input
  • social_api_list_keysreads sensitive data
  • social_api_list_webhook_deliveriesnetwork egress
  • social_api_list_webhooksnetwork egress
  • social_api_retry_webhook_deliverynetwork egress
  • social_api_revoke_keyreads sensitive data
  • social_api_test_webhooknetwork egress
  • social_api_update_webhooknetwork egress
  • social_api_connect_accountno sensitive capability
  • social_api_create_brandno sensitive capability
  • social_api_create_inviteno sensitive capability
  • social_api_create_keyno sensitive capability
  • social_api_create_postno sensitive capability
  • social_api_delete_brandno sensitive capability
  • social_api_delete_commentno sensitive capability
  • social_api_delete_mediano sensitive capability
  • social_api_delete_postno sensitive capability
  • social_api_delete_review_replyno sensitive capability
  • social_api_disconnect_accountno sensitive capability
  • social_api_events_summaryno sensitive capability
  • social_api_exchange_oauthno sensitive capability
  • social_api_get_account_limitsno sensitive capability
  • social_api_get_comment_repliesno sensitive capability
  • social_api_get_constraintsno sensitive capability
  • social_api_get_conversationno sensitive capability
  • social_api_get_meno sensitive capability
  • social_api_get_mentionsno sensitive capability
  • social_api_get_postno sensitive capability
  • social_api_get_postsno sensitive capability
  • social_api_get_reviewsno sensitive capability
  • social_api_get_storage_usageno sensitive capability
  • social_api_get_usageno sensitive capability
  • social_api_hide_commentno sensitive capability
  • social_api_like_commentno sensitive capability
  • social_api_list_account_pagesno sensitive capability
  • social_api_list_accountsno sensitive capability
  • social_api_list_brandsno sensitive capability
  • social_api_list_conversationsno sensitive capability
  • social_api_list_exportsno sensitive capability
  • social_api_list_invitesno sensitive capability
  • social_api_list_mediano sensitive capability
  • social_api_list_messagesno sensitive capability
  • social_api_list_post_commentsno sensitive capability
  • social_api_list_postsno sensitive capability
  • social_api_mark_conversation_readno sensitive capability
  • social_api_moderate_commentno sensitive capability
  • social_api_patch_meno sensitive capability
  • social_api_private_reply_to_commentno sensitive capability
  • social_api_reply_to_commentno sensitive capability
  • social_api_reply_to_reviewno sensitive capability
  • social_api_retry_postno sensitive capability
  • social_api_revoke_inviteno sensitive capability
  • social_api_send_dmno sensitive capability
  • social_api_send_feedbackno sensitive capability
  • social_api_unhide_commentno sensitive capability
  • social_api_unlike_commentno sensitive capability
  • social_api_unpublish_postno sensitive capability
  • social_api_update_account_pageno sensitive capability
  • social_api_update_brandno sensitive capability
  • social_api_update_conversationno sensitive capability
  • social_api_update_postno sensitive capability
  • social_api_update_review_replyno sensitive capability
  • social_api_validate_postno sensitive capability
  • social_api_verify_media_uploadno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.0 latest A 93/100 3 1.13.0 2026-09-09

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-socialapi/badge.svg)](https://mcptrustchecker.com/registry/mcp-socialapi)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-socialapi"><img src="https://mcptrustchecker.com/registry/mcp-socialapi/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-socialapi/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-socialapi --online

Use the free API → How scoring works

More in Developer Tools