io.github.luarss/alternativespe-mcp

Registre officiel Autres

Private-market data across Southeast Asia via the Alternatives Partner API v3

Que pouvez-vous faire avec io.github.luarss/alternativespe-mcp ?

  • 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), plus search, ordering, limit, offset.
  • Detail-by-UUID tools for every core entity.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package alternativespe-mcp
Claude Code
claude mcp add alternativespe-mcp -e 'ALTDMP_API_KEY=<your altdmp_api_key>' -e 'ALTDMP_BASE_URL=<ALTDMP_BASE_URL>' -- npx -y alternativespe-mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "alternativespe-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "alternativespe-mcp@0.1.1"
            ],
            "env": {
                "ALTDMP_API_KEY": "<your altdmp_api_key>",
                "ALTDMP_BASE_URL": "<ALTDMP_BASE_URL>"
            }
        }
    }
}

Variables d'environnement

  • ALTDMP_API_KEY obligatoire secret Your Alternatives Partner API key (obtain from support@alternatives.pe)
  • ALTDMP_BASE_URL Override the API base URL (default: https://api.altdmp.io/v3)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. alternativespe-mcp
  2. Features
  3. Tools
  4. Setup
  5. Usage with Claude Desktop / Claude Code
  6. Filtering
  7. Notes
  8. Environment variables
  9. Publishing
  10. License

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), plus search, ordering, limit, offset.
  • Detail-by-UUID tools for every core entity.

Tools

ToolEndpointDescription
search_capital_receiversPOST /capital-receivers/Funded companies / startups
get_capital_receiverGET /capital-receivers/{uuid}/Company detail: financials, cap table, investors, deals, news
search_capital_allocatorsPOST /capital-allocators/Investors (VC/PE, corporates, family offices)
get_capital_allocatorGET /capital-allocators/{uuid}/Investor detail: investments, AUM, commitments, funds, news
search_fundsPOST /funds/Funds (Atlas tier)
get_fundGET /funds/{uuid}/Fund detail: performance, AUM, commitments, investments
search_peoplePOST /people/Founders, directors, executives
get_personGET /people/{uuid}/Person detail: roles, investments, news
search_service_providersPOST /service-providers/Auditors, legal & professional services
search_investorsPOST /investors/Cross-entity investor discovery
get_reference_dataGET /reference-data/Enums, countries, industries, themes

Setup

npm install
npm run build

Set your API key (obtain credentials from support@alternatives.pe):

export ALTDMP_API_KEY=your_api_key_here

Usage with Claude Desktop / Claude Code

Add to your MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "alternativespe": {
      "command": "node",
      "args": ["/absolute/path/to/alternativespe-mcp/dist/index.js"],
      "env": {
        "ALTDMP_API_KEY": "your_api_key_here"
      }
    }
  }
}

Or, for local development without building:

{
  "mcpServers": {
    "alternativespe": {
      "command": "npx",
      "args": ["tsx", "/absolute/path/to/alternativespe-mcp/src/index.ts"],
      "env": { "ALTDMP_API_KEY": "your_api_key_here" }
    }
  }
}

Filtering

filters is forwarded verbatim as the API's filters body. Combine logical groups with conditions:

{
  "filters": {
    "all": [
      { "op": "eq", "field": "domicile_country_iso_alpha3", "value": "SGP" },
      { "op": "gte", "field": "latest_valuation_usd", "value": 50000000 },
      { "any": [
        { "op": "eq", "field": "is_raising_now", "value": true },
        { "op": "in", "field": "themes_keys", "value": ["themes_payments"] }
      ]}
    ]
  },
  "limit": 50,
  "ordering": "-latest_valuation_usd"
}

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

VariableRequiredDefaultDescription
ALTDMP_API_KEYyes—Your Alternatives Partner API key
ALTDMP_BASE_URLnohttps://api.altdmp.io/v3API base URL override

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:

FieldValue
Organization / userluarss
Repositoryalternativespe-mcp
Workflow filenamepublish-mcp-registry.yml
Environmentrelease

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

WTFPL

Questions fréquentes

Qu'est-ce que io.github.luarss/alternativespe-mcp ?

Private-market data across Southeast Asia via the Alternatives Partner API v3

Comment installer io.github.luarss/alternativespe-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add alternativespe-mcp -e 'ALTDMP_API_KEY=<your altdmp_api_key>' -e 'ALTDMP_BASE_URL=<ALTDMP_BASE_URL>' -- npx -y alternativespe-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.luarss/alternativespe-mcp ?

Oui. Il attend ALTDMP_API_KEY, à renseigner dans sa configuration.

io.github.luarss/alternativespe-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence WTFPL.

Qui maintient io.github.luarss/alternativespe-mcp ?

Il est publié par luarss. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.