---
title: "Discussion on \"I re-check 104 finance MCP servers, skills and APIs every week. Here's what breaks\" | Hashnode"
description: "Discussion on \"I re-check 104 finance MCP servers, skills and APIs every week. Here's what breaks\". A weekly GitHub Action verifies every tool in a finance AI directory. 84 of 104 pass. Here are the rules, the code and the surprises."
url: "https://hashnode.com/posts/i-re-check-104-finance-mcp-servers-skills-and-apis-every-week-here-s-what-breaks/6ae37cf6cdf6d15a93027c13"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [I re-check 104 finance MCP servers, skills and APIs every week. Here's what breaks](https://tradingaihub.hashnode.dev/i-re-check-104-finance-mcp-servers-skills-and-apis-every-week-here-s-what-breaks?utm_source=hashnode&utm_medium=feed)

A weekly GitHub Action verifies every tool in a finance AI directory. 84 of 104 pass. Here are the rules, the code and the surprises.

Oct 29 · 7 min read · tradingaihub.hashnode.dev  
Updated Nov 11  
Read the article

-   [#opensource](https://hashnode.com/tag/opensource)
-   [#fintech](https://hashnode.com/tag/fintech)
-   [#ai](https://hashnode.com/tag/ai)
-   [#mcp](https://hashnode.com/tag/mcp)

## Written by

[TradingAIHub](https://hashnode.com/@tradingaihub)

@tradingaihub

  
[View profile](https://hashnode.com/@tradingaihub)

Verified AI tools for finance & trading

Independent directory of finance MCP servers, AI agent skills and market-data APIs, re-checked every week for maintenance, package provenance and pricing. Free, in 13 languages. Not investment advice.

## Responses 2

Markdown supported · ⌘↵ to post

[Neurobro](https://hashnode.com/@neurobro)

[Nov 1](https://hashnode.com/posts/i-re-check-104-finance-mcp-servers-skills-and-apis-every-week-here-s-what-breaks/6ae37cf6cdf6d15a93027c13/comment/6ae700e00f03c9cdad00f411)

The package ownership check is the one I'd steal. 10 of 104 pointing at a name someone else owns on npm or PyPI is a real install-time risk, not just a stale badge. On the threshold, I'd almost split it - 180 days feels fine for a read-only market data server but way too loose for anything that touches a broker account. Have you thought about weighting it by what the tool can actually do?

[TradingAIHub](https://hashnode.com/@tradingaihub)

[Nov 10](https://hashnode.com/posts/i-re-check-104-finance-mcp-servers-skills-and-apis-every-week-here-s-what-breaks/6ae37cf6cdf6d15a93027c13/comment/6ae700e00f03c9cdad00f411#reply-6af3471da7b748d4ed20a1ec)

Hi Neurobro, thank you for this, especially the point that package provenance is an install-time risk, not just a stale badge.

You're right that a single 180-day threshold is too loose for anything that can reach a broker account. We're reviewing a risk-weighted re-verification schedule: a shorter interval for tools that can place orders or access brokerage credentials, and a longer window for read-only market-data servers. We also want the package-provenance result to be easier to see on tool pages.

We'll update this thread when that change is in place.

The TradingAIHub team
