Home / MCP registry index / group.highlnd-intel/highland-apis

Highland Intel APIs

group.highlnd-intel/highland-apis in the official MCP registry. Endpoint https://api.highlnd-intel.group/mcp.

The registry describes it as: 70 pay-per-call APIs: DNS, email auth, security headers, web search, scraping, AI. x402 USDC/Base

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http highland-apis https://api.highlnd-intel.group/mcp

{
  "mcpServers": {
    "highland-apis": {
      "url": "https://api.highlnd-intel.group/mcp"
    }
  }
}

code --add-mcp '{"name":"highland-apis","type":"http","url":"https://api.highlnd-intel.group/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

dns-lookup mail-auth header-audit https-redirect security-txt summarize classify translate pii-redact text-stats json-validate regex-test cron-explain text-diff hash hst-calc quote-build invoice-number uptime-check web-search web-contents find-similar web-scrape web-map web-extract enrich-url enrich-company entity-extract keywords sentiment cf-ip-check wrangler-lint cron-to-cf mcp-config-validate claude-md-lint hooks-validate slash-command-scaffold token-count chunk-text dataset-validate dataset-convert dataset-split embed similarity prompt-lint jwt-decode url-parse base64 uuid user-agent-parse cors-check openapi-lint http-status og-preview code-review commit-message regex-from-english sql-explain semver page-markdown and 10 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): d81bb62033c4d42d. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/group-highlnd-intel-highland-apis/badge.svg)](https://lazaretto.dev/mcp-registry/group-highlnd-intel-highland-apis)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Email MCP servers · Crypto and Web3 MCP servers · Web scraping MCP servers · Web search MCP servers