Omnisocials MCP Server

@omnisocials/mcp-server npm v1.33.0

Published by @omnisocials — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for OmniSocials API - manage social media posts, media, accounts, analytics, and webhooks

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

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

  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • rotate_webhook_secretnetwork egress
  • update_webhooknetwork egress
  • approve_postno sensitive capability
  • check_media_compatibilityno sensitive capability
  • create_and_publish_postno sensitive capability
  • create_folderno sensitive capability
  • create_hashtag_setno sensitive capability
  • create_postno sensitive capability
Show 34 more tools ↓
  • delete_hashtag_setno sensitive capability
  • delete_postno sensitive capability
  • get_accountno sensitive capability
  • get_account_analyticsno sensitive capability
  • get_analytics_overviewno sensitive capability
  • get_best_timesno sensitive capability
  • get_inbox_conversationno sensitive capability
  • get_postno sensitive capability
  • get_post_analyticsno sensitive capability
  • get_posts_analyticsno sensitive capability
  • get_recent_platform_postsno sensitive capability
  • get_webhookno sensitive capability
  • hide_inbox_replyno sensitive capability
  • list_accountsno sensitive capability
  • list_approval_workflowsno sensitive capability
  • list_foldersno sensitive capability
  • list_hashtag_setsno sensitive capability
  • list_inbox_conversationsno sensitive capability
  • list_mediano sensitive capability
  • list_postsno sensitive capability
  • list_webhooksno sensitive capability
  • list_workspacesno sensitive capability
  • mark_inbox_readno sensitive capability
  • publish_postno sensitive capability
  • reject_postno sensitive capability
  • reply_to_inboxno sensitive capability
  • retry_postno sensitive capability
  • search_instagram_audiono sensitive capability
  • search_locationsno sensitive capability
  • switch_workspaceno sensitive capability
  • update_hashtag_setno sensitive capability
  • update_mediano sensitive capability
  • update_postno sensitive capability
  • upload_mediano sensitive capability

What this scan could not see

Versions 10

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.33.0 latest A 95/100 0 1.13.0 2026-09-07
v1.32.0 A 95/100 0 1.13.0 2026-09-06
v1.31.0 A 95/100 0 1.13.0 2026-09-01
v1.29.0 A 95/100 0 1.13.0 2026-08-30
v1.28.0 A 95/100 0 1.13.0 2026-08-28
Show 5 more versions ↓
v1.27.0 A 95/100 0 1.13.0 2026-08-25
v1.24.0 A 95/100 0 1.12.1 2026-08-22
v1.22.0 A 95/100 0 1.12.1 2026-08-20
v1.21.0 A 95/100 0 1.12.1 2026-08-13
v1.20.1 A 95/100 0 1.12.1 2026-08-10

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/omnisocials-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/omnisocials-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/omnisocials-mcp-server"><img src="https://mcptrustchecker.com/registry/omnisocials-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/omnisocials-mcp-server/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 @omnisocials/mcp-server --online

Use the free API → How scoring works

More in Productivity & Workflow