
Alternativespe Mcp
io.github.luarssPublished by GitHub account luarssv0.1.1Updated Nov 3, 2026
Private-market data across Southeast Asia via the Alternatives Partner API v3
Overview
Read-only MCP access to Southeast Asian private-market data (companies, investors, funds, people) via the Alternatives Partner API v3.
- What you can do
- Search and filter funded companies and startups, then open a company's detail record with financials, cap table, investors, deals and news
- Search and inspect investors (VC/PE, corporates, family offices) and their investments, AUM, commitments and funds
- Search funds and retrieve fund detail such as performance, AUM, commitments and investments
- Search people such as founders, directors and executives, and read their roles, investments and news
- Search service providers (auditors, legal and professional services) and run cross-entity investor discovery
- Fetch reference data such as enums, countries, industries and themes to build valid filters
- When to use it
- Useful when an assistant needs to research or screen Southeast Asian private-market companies, investors, funds or people, for example sourcing deals, mapping investors or checking a company's funding history. It suits users who already have an Alternatives Partner API subscription.
- Requirements
- Runs as a local Node.js process, installed from the npm package alternativespe-mcp (build with npm install and npm run build, or run via npx tsx). Requires an Alternatives Partner API key in the ALTDMP_API_KEY environment variable, obtained from the provider's support address. ALTDMP_BASE_URL can optionally override the API base URL. Network access to the API is needed.
Installation
In SourceWeft
- Open Alternativespe Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
alternativespe-mcp
An MCP server for the Alternatives Partner API v3 (altdmp.io) — read-only programmatic access to private-market data across Southeast Asia (funded companies, investors, funds, people, service providers).
Features
- Handles the API-key → bearer-token exchange automatically, with token caching/refresh.
- Exposes each list endpoint with the full POST filter tree (
all/any/not+ operators), plussearch,ordering,limit,offset. - Detail-by-UUID tools for every core entity.
Tools
Setup
Set your API key (obtain credentials from [email protected]):
Usage with Claude Desktop / Claude Code
Add to your MCP config (e.g. claude_desktop_config.json):
Or, for local development without building:
Filtering
filters is forwarded verbatim as the API's filters body. Combine logical groups with conditions:
Operators: eq, in (array), gt, gte, lt, lte, range (2-element array), contains, isnull.
Logical groups: all (AND), any (OR), not (negate).
Use get_reference_data to discover valid field enum values.
Notes
- Rate limit: 320 requests / rolling 60-second window (enforced by the API).
- Subscription tiers: Atlas (all endpoints) and Allocate (excludes funds and allocator commitments).
- Tokens are valid for 24 hours; this server refreshes them automatically.
Environment variables
Publishing
Both npm and the MCP Registry publish via OIDC — no long-lived tokens are stored in this repo.
npm (Trusted Publishing / OIDC)
Automated publishing uses npm Trusted Publishing: GitHub Actions authenticates to npm over short-lived OIDC and provenance is generated automatically — no NPM_TOKEN.
One-time setup on npmjs.com (after the first version exists — see bootstrapping below): package Settings → Trusted Publisher → GitHub Actions, set:
Bootstrapping: a trusted publisher can only be configured once the package already exists, so the very first version must be published manually — npm publish --access public locally — then configure the trusted publisher for all subsequent releases.
MCP Registry
server.json is published to the official MCP Registry via the mcp-publisher CLI using GitHub OIDC (mcp-publisher login github-oidc) — also tokenless.
Automated release
Pushing a v* tag (e.g. git tag v0.1.0 && git push origin v0.1.0) triggers .github/workflows/publish-mcp-registry.yml. The job runs in the protected release GitHub environment (required reviewer + v*-tags-only), so a publish waits for manual approval, then publishes to npm (OIDC) and syncs server.json's version to the tag before publishing it to the registry (OIDC).
License
Source: README.md at commit 1eedd26
Tools
0Version history
1- v0.1.1LatestSep 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts