# finmap-org/mcp-server — health index 58/100 (Moderate)

> Inspection of the public repository finmap-org/mcp-server by inspect.software. It holds a health index of 58 out of 100, placing it in the Moderate band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/finmap-org/mcp-server
- Report page: https://inspect.software/software/finmap-org/mcp-server
- Full JSON report: https://inspect.software/api/repositories/finmap-org/mcp-server/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/f/finmap-org/mcp-server.svg
- Inspected: 2026-07-17
- Methodology: metrics 1.13.0, report schema 0.12.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 85/100 | Excellent |
| Community & Adoption | 18% | 39/100 | At risk |
| Sustainability & Governance | 24% | 52/100 | Moderate |
| Engineering Quality | 20% | 56/100 | Moderate |
| Security | 16% | 56/100 | Moderate |
| AI Readiness | not counted | 38/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | The finmap.org MCP server provides comprehensive historical data from the US, UK, Russian and Turkish stock exchanges. Access sectors, tickers, company profiles, market cap, volume, value, and trade counts, as well as treemap and histogram visualizations |
| Homepage | https://npmjs.com/finmap-mcp |
| Primary language | TypeScript |
| License | LGPL-3.0 |
| Stars | 12 |
| Forks | 4 |
| Created | 2025-08-20 |
| Last push | 2026-07-14 |
| Latest release | v3.2.10 |
| Commits (last year) | 115 |
| Bus factor | 1 |
| Topics | ai-agents, ai-tools, borsa-istanbul, exchange, lse, mcp, mcp-server, moex, moscow-exchange, nasdaq, nyse, stock-market, london-stock-exchange, agentic, financial-data, historical-data, market-capitalization, market-data, modelcontextprotocol, stock-exchange |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | finmap-mcp | 3.2.10 | 1,105 |

## Vitality — 85/100 (Excellent)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 82/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 3 days ago |
| Commit cadence | partial | 18 / 36 | 26/52 weeks with commits |
| Commit volume | met | 18 / 18 | 115 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |

### Release discipline — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 37 releases published |
| Release recency | met | 36 / 36 | latest release 3 days ago |
| Release cadence | met | 27 / 27 | a release every ~9 days |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 39/100 (At risk)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 21/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 16.9 / 60 | 12 stars |
| Forks | partial | 4 / 25 | 4 forks |
| Watchers | not met | 0 / 15 | 1 watchers |

### Community health — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (LGPL-3.0) |
| CONTRIBUTING guide | not met | 0 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 51/100 (Moderate)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 40.6 / 80 | 1,105 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 52/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 27/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 8 / 22.5 | top contributor authored 64% of commits |
| Contributor breadth | partial | 4.1 / 13.5 | 3 contributors |
| OpenSSF Scorecard: Contributors | partial | 6 / 10 | project has 2 contributing companies or organizations -- score normalized to 6 |

### Issue & PR responsiveness — 50/100 (Moderate)

Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | partial | 26.5 / 38.2 | 9/13 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 46/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 5 / 25 | 4 followers of finmap-org |
| Track record | partial | 11.5 / 25 | 13 public repos, account ~1 yr old |

### Package maintenance — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on npm |
| Publish recency | met | 35 / 35 | latest publish 3 days ago |
| Version history | met | 20 / 20 | 33 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 56/100 (Moderate)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 50/100 (Moderate)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 2 workflow(s) |
| Tests present | not met | 0 / 24 | — |
| Linter config | met | 16 / 16 | biome.json |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | no pull request found |

### Documentation — 65/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://npmjs.com/finmap-mcp |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 20 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 56/100 (Moderate)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 56/100 (Moderate)

Excluded from scoring (no data or not applicable): CI-Tests. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | excluded | 0 / 2.5 | no pull request found |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | partial | 1.5 / 2.5 | project has 2 contributing companies or organizations -- score normalized to 6 |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | partial | 1.5 / 5 | dependency not pinned by hash detected -- score normalized to 3 |
| SAST | not met | 0 / 5 | no SAST tool detected |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | partial | 6.8 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

## AI Readiness — 38/100 (At risk)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 1/100 (Critical)

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 43/100 (At risk)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | not met | 0 / 22 | — |
| Lint / format config | met | 11 / 11 | biome.json |
| Static type checking | met | 11 / 11 | tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 3 / 10 | dependency not pinned by hash detected -- score normalized to 3 |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | met | 55 / 55 | 0/7 source files over 60KB |

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt