Blind
PYPI · BLIND-MCP
What a role really pays, including markets where the employer publishes no range.
Available components
Last scanned (23 hours ago)
Scores higher than 82% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to dheerajjha/blind-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1099 tokens (~137/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_bands" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +11
- Malware scan: unverified → pass ▲ security
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.77 functional
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → pass ▲ functional
- 2 Nov 26 −1
- Security disclosure: pass → unverified ▼ functional
- 31 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed pypi/blind-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dheerajjha/blind-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dheerajjha/blind-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 2857657788 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:a17bba523b2badfef6e118c3bd20d5572ef9e3fac28f3b94a34a4cac5369ff2b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
company_posts ~67
List posts about a company, optionally narrowed to one topic. `topic` accepts a bare keyword from company_topics (e.g. "india", "wlb").
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| limit | integer | – | – |
| page | integer | – | – |
| topic | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
company_topics ~65
List the discussion topics Blind itself suggests for a company. These are the highest-signal entry points -- e.g. Roku exposes india, wlb, culture, layoffs, interview, rsu. Use one as the `topic` for company_posts.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find ~258
Find a company's posts about one keyword. This is how you search Blind. The company topic path accepts any keyword, so `find("Intuit", "maternity")` returns exactly the maternity threads -- which paging the main listing will not surface, since they can be years deep. Prefer one distinctive noun ("maternity", "rto", "refresher"); vague words like "policy" match hundreds of loosely-related posts. Fetches only the requested page (1-based); pagination is caller-driven. `total_matches` counts all matches, while `posts` contains at most `limit` cards from this page. `max_page` is the last page linked by Blind (defaults to 1 if no pagination is present). Request page=2, etc. to see more; use a larger limit to avoid truncating cards within a page. `limit=0` returns metadata only. An empty later page is normal: stop paging, not a signal that the keyword has no matches. An empty first page means no matches. Never falls back to the generic listing.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| keyword | string | yes | – |
| limit | integer | – | – |
| page | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
job_openings ~136
List a company's open roles, with the pay range where one is published. Reads the company's public job-board API (Greenhouse, Ashby or Lever). `role` filters to titles containing every word you give, so "forward deployed" matches "AI Engineer - FDE (Forward Deployed Engineer)". Not every employer is reachable: Google, Meta, Amazon and Apple self-host their careers sites and are not on these boards.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| company | string | yes | – |
| limit | integer | – | – |
| role | string | – | – |
| with_pay_only | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
market_rate ~133
Compare what a role pays across several companies at the same seniority. One company's band tells you what that company pays; several tell you whether an offer is competitive. Pass `level` (mid, senior, staff, lead, principal, manager, senior_manager, director) to compare like with like -- without it, each company's largest band is used, which may not be the same rung. Companies not on Greenhouse, Ashby or Lever are listed under `unreachable` rather than silently dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| level | string | – | – |
| role | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pay_bands ~249
What a role pays at one company, broken down by seniority. Colorado, California, New York, Washington and Illinois require a salary range on covered postings; India, Singapore and most of the EU require none. So the same title at the same company carries a band in Denver and nothing in Bengaluru, and the published one is the best available anchor for the silent one -- same employer, same title, same week. Bands are reported per level, because a single range across seniorities is a number nobody is offered: "forward deployed" at Databricks spans 140,400-320,200 undivided, but resolves into a mid band, a senior band carried by 48 postings, and several management bands. `typical` is the modal band -- the one the most postings carry -- and is usually what you want. `distinct_bands` versus `postings` shows how much independent evidence there is: 48 postings sharing one band is one data point advertised 48 times, not 48 data points.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| company | string | yes | – |
| role | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_post ~75
Read one Blind post in full. Returns the body, Blind's own AI summary of the comment thread, and the comments with each commenter's employer -- which is how you weigh a claim (an answer from someone at the company differs from a passer-by).
| Name | Type | Req | Description |
|---|---|---|---|
| max_comments | integer | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
research ~116
Answer a question about a company by pulling the most relevant threads. Probes the distinctive words in the question against Blind's keyword-scoped company pages, merges the hits, then returns the best threads in full with Blind's own AI summary and the comments that actually address the question. Ask naturally: "how many days in office in India", "what is the maternity leave policy", "do they require a PhD".
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| max_posts | integer | – | – |
| question | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Blind MCP server?
Blind runs locally as a PyPI package, launched with uvx blind-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · blind-mcp
claude mcp add dheerajjha-blind-mcp -- uvx blind-mcp
What is the Blind MCP server?
Blind is an MCP server listed in the public MCP registry as io.github.dheerajjha/blind-mcp. What a role really pays, including markets where the employer publishes no range. This page covers its PyPI package (blind-mcp).
Is the Blind MCP server safe to use?
Blind scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Blind MCP server expose?
Blind exposes 8 tools: company_topics, company_posts, read_post, find, research, and 3 more. Their descriptions and schemas cost roughly 1,099 tokens of context every time the server is loaded.
Is the Blind MCP server still maintained?
Blind is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Blind MCP server under?
Blind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Blind MCP server?
VerifyMCP ran 15 checks on Blind, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Blind: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.