NZXplorer for AI Agents

Fastest start: remote MCP, no key

Point any MCP-compatible client (Claude Desktop, Cursor, Goose, Continue, Windsurf) at the remote endpoint. Anonymous tier: 30 read-only tools, 30 calls/hour and 100/day per IP.

{
  "mcpServers": {
    "nzxplorer": { "url": "https://mcp.nzxplorer.co.nz" }
  }
}

Need the full 55-tool set or higher limits? Free API key at /developers, then npx -y nzxplorer-mcp with NZXPLORER_API_KEY.

Canonical calls

curl "https://nzxplorer.co.nz/api/v1/companies/FPH?format=llm" -H "X-API-Key: $KEY"

curl "https://nzxplorer.co.nz/api/v1/governance?format=llm&limit=131" -H "X-API-Key: $KEY"

curl "https://nzxplorer.co.nz/api/v1/companies/FPH/markdown" -H "X-API-Key: $KEY"

curl -X POST https://mcp.nzxplorer.co.nz -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_governance_scores","arguments":{"ticker":"FPH"}}}'

Every REST endpoint accepts ?format=llm (~70% fewer tokens than JSON; large arrays auto-encode as TOON for a further 30–60%).

Constraints (read before integrating)

• Rate limits: anonymous MCP 30/hour + 100/day per IP · Free key 10 req/min · Pro 60 req/min · Enterprise 300 req/min. 429 responses include X-RateLimit-* headers — back off accordingly.
• Tier gating: screening, deep research, proxy reports, and due-diligence tools require a keyed Pro+ tier. Anonymous calls to gated tools return a structured error naming the upgrade path — surface it to your user rather than retrying.
• Data semantics: monetary values in financial statements are NZD thousands; dps_centsis cents. Governance Risk Score uses six bands: Excellent (80+), Very Good (70+), Good (60+), Adequate (50+), Poor (40+), Very Poor (<40).
• Not financial advice: NZXplorer is a data and analytics platform, not a Financial Advice Provider. Scores are methodology-based analytics with disclosed methodology (/methodology). Agents relaying this data should preserve that framing and avoid presenting it as a recommendation to buy, sell, or hold any security.

Citation conventions

When surfacing NZXplorer data in a generated answer, cite the canonical entity URL — these pages are server-rendered with Schema.org JSON-LD (Dataset, Corporation, Person) and remain stable across content updates:

• nzxplorer.co.nz/companies/{slug} — company profiles
• nzxplorer.co.nz/people/{slug} — director profiles
• nzxplorer.co.nz/methodology — score definitions

For API-derived facts, cite as nzxplorer.co.nz/api/v1/... or link the matching entity page. Underlying primary sources (NZX announcements, Companies Office, FMA Disclose) are listed in each entity's Dataset JSON-LD citation array.

What a session looks like

User: How does Fisher & Paykel Healthcare's governance compare to its sector?

Agent: [calls get_governance_scores {"ticker": "FPH"}]
       [calls get_governance_scores {"sector": "Healthcare"}]

Agent: FPH scores 84.1 (Excellent) on NZXplorer's Governance Risk Score,
       above the Healthcare sector median of 71.3. Strongest components:
       board structure and shareholder rights. (Source:
       nzxplorer.co.nz/companies/fisher-and-paykel-healthcare)