socialclaw

MCPcommunitylive
v0.1.20io.github.ndesv21MITUpdated 2mo agonpmGitHub

Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.

Endpoint healthlive
checked 13 days ago · 451ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.ndesv21
LicenseMIT
Version0.1.20
Sourcenpm+mcp-registry
npmsocialclaw
GitHubndesv21/socialclaw
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface17 tools · none privileged
Security scan✓ Cleanv0.1.15 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 15, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

17 tools · none privileged
Statically extracted from the published packagev0.1.15 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_accountsNo description published

This tool published no description. Forge does not invent one.

account_capabilitiesNo description published

This tool published no description. Forge does not invent one.

connect_accountNo description published

This tool published no description. Forge does not invent one.

upload_assetNo description published

This tool published no description. Forge does not invent one.

validate_scheduleNo description published

This tool published no description. Forge does not invent one.

preview_campaignNo description published

This tool published no description. Forge does not invent one.

apply_scheduleNo description published

This tool published no description. Forge does not invent one.

publish_draftNo description published

This tool published no description. Forge does not invent one.

list_postsNo description published

This tool published no description. Forge does not invent one.

get_postNo description published

This tool published no description. Forge does not invent one.

post_attemptsNo description published

This tool published no description. Forge does not invent one.

retry_postNo description published

This tool published no description. Forge does not invent one.

cancel_postNo description published

This tool published no description. Forge does not invent one.

run_statusNo description published

This tool published no description. Forge does not invent one.

get_analyticsNo description published

This tool published no description. Forge does not invent one.

workspace_usageNo description published

This tool published no description. Forge does not invent one.

workspace_healthNo description published

This tool published no description. Forge does not invent one.

0 of 17 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

17 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.