CanopiiCanopiiAll serversEnterprise →
io.github.TwitterAPIs/twitterapis-mcp

io.github.TwitterAPIs/twitterapis-mcp v0.9.8

Security Trust Score
Grade B · Moderate posture
Tier 1 · Public sourceHigh confidence · 98%
Declared MCP capabilities
ResourcesPrompts

Host io.github.TwitterAPIs/twitterapis-mcp in a governed environment — SSO in front, every tool call attributed and audited.

Reputation0stars1forks3.2kdownloads/mo0open issues10d agolast commit<1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Tool Definition Integrityguard2 tool description(s) drifted after publish (no risk signals in diff)

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

    twitter_user_tweets_completetwitter_customer_session

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    Strict JSON Schema EnforcementadditionalProperties:false present

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Application Security Checks

  • Warn
    No path traversalguard1 occurrence

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

    src/feedback.js:113

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard1 occurrence

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    src/index.js:185

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    Dependencies pinned (lockfile)no lockfile found

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

    Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).

  • Warn
    Published with provenanceno provenance attestation

    Build provenance attests the artifact was built from the claimed source by CI.

    Fix: Publish with npm provenance (--provenance) from a trusted CI.

  • Warn
    Established maintainersingle maintainer

    Brand-new / single anonymous maintainers raise takeover and malware risk.

    Fix: Publish under an established account/org; add multiple maintainers.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    No known-vulnerable dependencies1 runtime deps, no known CVEs

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

  • Pass
    No install/post-install scriptsguardno install scripts

    install hooks run arbitrary code on every consumer at install time.

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseMIT

    A clear license is required for legal enterprise use.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (80)

twitter_mutingtwitter_trendstwitter_dm_listtwitter_dm_sendtwitter_retweettwitter_blockingtwitter_bookmarkstwitter_grok_chattwitter_unretweettwitter_user_infotwitter_account_metwitter_user_abouttwitter_user_likestwitter_user_logintwitter_user_mediatwitter_follow_usertwitter_grok_configtwitter_list_createtwitter_list_tweetstwitter_spaces_infotwitter_user_searchtwitter_user_statustwitter_user_tweetstwitter_create_tweettwitter_delete_tweettwitter_list_memberstwitter_media_statustwitter_media_uploadtwitter_tweet_detailtwitter_tweet_quotestwitter_tweet_threadtwitter_feedback_listtwitter_feedback_sendtwitter_home_timelinetwitter_list_timelinetwitter_tweet_repliestwitter_unfollow_usertwitter_user_mentionstwitter_article_createtwitter_bookmark_tweettwitter_community_infotwitter_favorite_tweettwitter_list_followerstwitter_user_followerstwitter_user_followingtwitter_advanced_searchtwitter_article_publishtwitter_bookmark_searchtwitter_community_abouttwitter_dm_conversationtwitter_list_add_membertwitter_user_affiliatestwitter_user_info_by_idtwitter_account_paymentstwitter_bookmark_folderstwitter_community_searchtwitter_community_tweetstwitter_customer_sessiontwitter_trends_locationstwitter_tweet_retweeterstwitter_unbookmark_tweettwitter_unfavorite_tweettwitter_article_unpublishtwitter_community_memberstwitter_user_followers_v2twitter_user_following_v2twitter_followers_you_knowtwitter_list_remove_membertwitter_article_update_titletwitter_community_moderatorstwitter_user_tweets_completetwitter_community_membershipstwitter_article_update_contenttwitter_customer_session_deletetwitter_customer_session_statustwitter_user_tweets_and_repliestwitter_user_verified_followerstwitter_bookmark_folder_timelinetwitter_check_follow_relationshiptwitter_article_update_cover_media

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "twitter_user_tweets_complete" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "twitter_customer_session" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.