Sf (PyPI) MCP Server

sf-mcp PyPI v0.1.2

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

Signal Found MCP server — connect AI agents to the world's largest Reddit outreach network

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−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 40

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

  • agent_quickstartno sensitive capability
  • billing_and_creditsno sensitive capability
  • change_crm_stateno sensitive capability
  • compare_confirmed_vs_uninterestedno sensitive capability
  • configure_product_strategyno sensitive capability
  • configure_targetingno sensitive capability
  • create_new_accountno sensitive capability
  • create_new_productno sensitive capability
  • crm_customers_by_stateno sensitive capability
  • crm_state_statsno sensitive capability
Show 30 more tools ↓
  • crm_workbenchno sensitive capability
  • current_client_contextno sensitive capability
  • get_conversation_by_idno sensitive capability
  • get_conversation_notesno sensitive capability
  • get_deduped_crm_by_categoryno sensitive capability
  • get_onboarding_prompt_packno sensitive capability
  • get_onboarding_statusno sensitive capability
  • get_product_treeno sensitive capability
  • list_campaignsno sensitive capability
  • list_conversion_statesno sensitive capability
  • list_productsno sensitive capability
  • login_with_client_idno sensitive capability
  • logout_client_contextno sensitive capability
  • modify_conversion_notesno sensitive capability
  • modify_funnelsno sensitive capability
  • modify_keywordsno sensitive capability
  • modify_market_positioningno sensitive capability
  • modify_subredditsno sensitive capability
  • onboarding_campaign_decisionno sensitive capability
  • portfolio_close_rateno sensitive capability
  • rebalance_resources_to_productno sensitive capability
  • run_full_agentic_onboardingno sensitive capability
  • sales_control_towerno sensitive capability
  • send_reddit_messageno sensitive capability
  • sf_healthno sensitive capability
  • submit_agent_targetingno sensitive capability
  • submit_onboarding_artifactsno sensitive capability
  • update_conversation_notesno sensitive capability
  • upsert_conversation_noteno sensitive capability
  • voice_of_customer_reportno sensitive capability

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
v0.1.2 latest A 98/100 0 1.13.0 2026-08-25

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

Use the free API → How scoring works

Other implementations of Sf 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Developer Tools