io.github.phdwight/pse-edge-mcp vs nepse.link
io.github.phdwight/pse-edge-mcp is an MCP server published by phdwight. Marketplaces we read that list it: 1 (Official MCP Registry). nepse.link is an MCP server published by nepse.link. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.phdwight/pse-edge-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.19.1 Downloads/month (PyPI): 248 Downloads/week (PyPI): 34 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.phdwight/pse-edge-mcp | nepse.link |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (pse.sakayandgo.com/mcp) | Remote server (nepse.link/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/phdwight/pse-edge-mcp | github.com/summonshr/nepse.link |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-26 |
| Endpoint at the last check (differs) | Responded 43 h ago, requires a key | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.phdwight/pse-edge-mcp
Philippine Stock Exchange data via PSE Edge: EOD quotes, price history, disclosures, financials.
nepse.link
Nepal Stock Exchange data: prices, company filings, signals, broker flow, IPOs, fund NAVs.
How to run each
io.github.phdwight/pse-edge-mcp As a remote MCP server
claude mcp add --transport http pse-edge-mcp https://pse.sakayandgo.com/mcpnepse.link As a remote MCP server
claude mcp add --transport http nepse https://nepse.link/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.phdwight/pse-edge-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.phdwight/pse-edge-mcp · What it can do: nepse.link · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.