Highland Intel APIs
REMOTE · API.HIGHLND-INTEL.GROUP
70 pay-per-call APIs: DNS, email auth, security headers, web search, scraping, AI. x402 USDC/Base
Available components
Last scanned (16 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9785 tokens (~139/item across 70 items; 70 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cors-check" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.highlnd-intel.group/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=highlnd-intel.group | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d92ab332b5c670fa0eb4778b88657d71 |
| SANs: highlnd-intel.group, api.highlnd-intel.group, *.api.highlnd-intel.group | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.highlnd-intel.group. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| group. | DS published | 23501, 63685 | 8, 8 | Verified |
| highlnd-intel.group. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.highlnd-intel.group/mcp | Verified | 200 | |
| http (plaintext) | http://api.highlnd-intel.group/mcp | HTTPS enforced | 301 | https://api.highlnd-intel.group/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
similarity Semantic similarity ranking ~130
Ranks up to 15 candidate texts by cosine similarity to a query, using @cf/baai/bge-base-en-v1.5 embeddings. Returns { model, ranked: [{ index, score }] (highest first), scores: number[] (input order) } Price: 3 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | 1 to 15 candidate texts, each up to 2000 characters. |
| query | string | yes | Query text, up to 2000 characters. |
No output schema declared.
No examples provided.
slash-command-scaffold Slash command scaffold ~169
Writes a ready-to-save Claude Code slash command file with frontmatter, $ARGUMENTS and a step outline. Returns { path, content, usage }: save content at path (.claude/commands/<name>.md). Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedTools | array | – | Optional tool rules the command may use, e.g. Read or Bash(git diff:*). |
| argumentHint | string | – | Optional hint for the arguments, e.g. [file] [focus]. |
| description | string | yes | One-line description shown in the / menu. |
| name | string | yes | Command name: lowercase letters, digits and -, up to 40 characters. |
No output schema declared.
No examples provided.
sql-explain SQL explainer ~93
Explains a SQL query step by step and flags performance and safety risks, with index suggestions. Returns { summary, steps, risks, index_suggestions } Price: 2 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | One SQL statement, up to 5,000 characters. It is not executed. |
No output schema declared.
No examples provided.
summarize Summarize ~114
Three-bullet summary of up to 8,000 characters. Input is PII-redacted first. Returns { summary }: up to three short bullet points as one string. Price: 4 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to process, 1 to 8,000 characters. Emails, phone numbers, card numbers, SINs and IPv4s are redacted before the model sees it. |
No output schema declared.
No examples provided.
text-diff Text diff ~119
Line-by-line diff of two texts (up to 500 lines each). Returns { added, removed, diff }: line counts and the diff lines prefixed with space, - or +. Price: 2 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | Original text, up to 32,000 characters and 500 lines. |
| b | string | yes | Changed text, up to 32,000 characters and 500 lines. |
No output schema declared.
No examples provided.
text-stats Text statistics ~92
Word, sentence and character counts, reading time and a Flesch reading-ease score. Returns { characters, words, sentences, readingMinutes, fleschReadingEase }. Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to measure, up to 64,000 characters. |
No output schema declared.
No examples provided.
token-count Token count estimate ~127
Estimated token counts for cl100k-like, o200k-like, Claude-like and Llama-like tokenizers plus a char/4 baseline. Deterministic estimates, not exact counts. Returns { estimates: { cl100k, o200k, claude, llama, char4 }, chars, bytes, pieces, method, exact: false } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to count, up to 60,000 characters. |
No output schema declared.
No examples provided.
tool-schema Tool schema generator ~132
Builds ready-to-paste tool definitions for Anthropic, OpenAI and MCP from a compact parameter spec. Returns { anthropic, openai, mcp } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the tool does. |
| name | string | yes | Tool name. |
| params | object | – | Map of parameter name to "type[:extra][!] description"; types string, number, integer, boolean, object, enum:a,b, array:itemtype; ! marks required. |
No output schema declared.
No examples provided.
translate Translate (EN/FR and more) ~156
Translates text between languages; defaults to English to French for NS/NB customers. Returns { translated, source, target }: the translated text and the language pair used. Price: 4 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | ISO 639-1 two-letter lower-case language code of the input text. |
| target | string | – | ISO 639-1 two-letter lower-case language code to translate into. |
| text | string | yes | Text to process, 1 to 8,000 characters. Emails, phone numbers, card numbers, SINs and IPv4s are redacted before the model sees it. |
No output schema declared.
No examples provided.
uptime-check Uptime check ~146
One HTTPS probe of a public domain: status, latency and whether it looks up. Returns { domain, up, status, ms }: up is true for any status below 500; status is null when the host does not answer. Price: 2 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name, e.g. example.com; IP literals and private suffixes (.local, .internal, .lan, .corp) are refused. |
| path | string | – | Path to probe, starting with /, letters, digits, _ . / - only. |
No output schema declared.
No examples provided.
url-parse URL parser ~129
Splits a URL into scheme, host, port, path segments, query (repeated keys as arrays) and fragment, with warnings for credentials, plain http and punycode. Passwords are never echoed. Returns { href, protocol, username, hasPassword, hostname, port, pathname, pathSegments, query, hash, origin, isIp, warnings } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute URL to parse. It is not fetched. |
No output schema declared.
No examples provided.
user-agent-parse User-agent parser ~114
Identifies browser, engine, OS, device class and known crawlers, AI bots and HTTP clients from a User-Agent string. Rule-based; user agents can be spoofed. Returns { browser: { name, version }, engine, os: { name, version }, device, isBot, bot } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| userAgent | string | yes | The User-Agent header value. |
No output schema declared.
No examples provided.
uuid UUID generator ~118
Generates 1 to 100 random v4 or time-ordered v7 UUIDs (RFC 9562) from Web Crypto. Returns { version, uuids: string[] } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many UUIDs, 1 to 100. |
| version | integer | – | 4 for random, 7 for Unix-ms time-ordered (sortable, good for database keys). |
No output schema declared.
No examples provided.
web-contents Web page contents ~122
Clean text of up to 5 public pages, capped per page, for agents to read. Returns { results: [{ url, title, publishedDate, text, characters }] }: one entry per page the provider could read. Price: 6 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| maxCharacters | integer | – | Text kept per page, 500 to 10,000 characters. |
| urls | array | yes | 1 to 5 public http(s) URLs. |
No output schema declared.
No examples provided.
web-extract Structured web extract ~228
Scrapes a public page and fills your flat schema (up to 20 typed fields) from it. Values are type-checked. Returns { url, finalUrl, title, data, missing }: one value per field (typed, or null when the page does not say) and the required fields that came back null. Price: 10 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | object | yes | Flat JSON Schema of what to extract: { type: "object", properties: { <name>: { type: string|number|integer|boolean, description?, enum? } }, required? }. 1 to 20 fields; names match ^[A-Za-z_][A-Za-z… |
| url | string | yes | Public http(s) URL. Private, loopback, link-local and metadata addresses, internal hostnames and this service's own hosts are refused. |
No output schema declared.
No examples provided.
web-map Site map ~165
Discovers the URLs of a public site (up to 200), optionally ranked by a search term. Returns { url, count, links }: up to 200 unique public URLs. Price: 6 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| includeSubdomains | boolean | – | Also include links on subdomains of the site. |
| limit | integer | – | Links to return, 1 to 200. |
| search | string | – | Optional term to rank and filter links by, up to 200 characters. |
| url | string | yes | Public http(s) URL. Private, loopback, link-local and metadata addresses, internal hostnames and this service's own hosts are refused. |
No output schema declared.
No examples provided.
web-scrape Web scrape to Markdown ~138
Main content of one public page as Markdown (up to 50,000 characters), with title and status. Returns { url, finalUrl, title, description, statusCode, markdown, characters, truncated }. Price: 7 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | integer | – | Markdown kept, 1,000 to 50,000 characters. |
| url | string | yes | Public http(s) URL. Private, loopback, link-local and metadata addresses, internal hostnames and this service's own hosts are refused. |
No output schema declared.
No examples provided.
web-search Web search ~210
Neural or keyword web search with highlights, for agents. Up to 10 results, public URLs only. Returns { query, results: [{ title, url, publishedDate, score, highlights }] }: up to 10 results, each with up to 3 highlights of 500 characters. Price: 8 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeDomains | array | – | Never return results from these domains (up to 20). |
| includeDomains | array | – | Only return results from these domains (up to 20). |
| numResults | integer | – | Results to return, 1 to 10. |
| query | string | yes | Search query, 1 to 500 characters. |
| startPublishedDate | string | – | Only pages published on or after this date (YYYY-MM-DD, UTC). |
| type | string | – | Search mode: auto (default), neural (semantic) or fast. |
No output schema declared.
No examples provided.
webhook-verify Webhook signature verifier ~209
Verifies Stripe, GitHub, Slack, Shopify or generic HMAC-SHA256 webhook signatures exactly as the provider computes them, with timestamp tolerance. Returns { provider, valid, timestamp?, age_s?, within_tolerance? } Price: 1 credit (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | string | yes | Raw request body exactly as received. |
| provider | string | yes | Signature scheme. |
| secret | string | yes | Webhook signing secret. Use a test secret; it is not stored. |
| signature | string | yes | Signature header value (Stripe-Signature, X-Hub-Signature-256, X-Slack-Signature, X-Shopify-Hmac-Sha256, or hex/base64). |
| timestamp | string | – | Slack only: X-Slack-Request-Timestamp. |
| tolerance_s | integer | – | Allowed clock skew for Stripe and Slack, default 300. |
No output schema declared.
No examples provided.
wrangler-lint Wrangler config lint ~161
Lints a wrangler.jsonc or wrangler.toml: name, entry point, compatibility date, secrets left in vars, routes. Returns { ok, format, findings[{ severity: error|warning|info, code, path, message }] and counts { error, warning, info } }. Values are never echoed, only paths. Price: 2 credits (1 credit = 1 CAD cent) per successful call; input that does not match the schema is rejected before billing.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The wrangler.jsonc, wrangler.json or wrangler.toml text, up to 60,000 characters. |
| format | string | – | Config format; auto treats text starting with { as JSONC, otherwise TOML. |
No output schema declared.
No examples provided.
How do I install the Highland Intel APIs MCP server?
Highland Intel APIs is a hosted endpoint at https://api.highlnd-intel.group/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.highlnd-intel.group
claude mcp add --transport http group-highlnd-intel-highland-apis 'https://api.highlnd-intel.group/mcp'
What is the Highland Intel APIs MCP server?
Highland Intel APIs is an MCP server listed in the public MCP registry as group.highlnd-intel/highland-apis. 70 pay-per-call APIs: DNS, email auth, security headers, web search, scraping, AI. x402 USDC/Base. This page covers its hosted endpoint (https://api.highlnd-intel.group/mcp).
Is the Highland Intel APIs MCP server safe to use?
Highland Intel APIs scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Highland Intel APIs MCP server expose?
Highland Intel APIs exposes 70 tools: dns-lookup, mail-auth, header-audit, https-redirect, security-txt, and 65 more. Their descriptions and schemas cost roughly 9,756 tokens of context every time the server is loaded.
Does the Highland Intel APIs MCP server require authentication?
No. We connected to Highland Intel APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Highland Intel APIs MCP server still maintained?
Highland Intel APIs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Highland Intel APIs MCP server?
VerifyMCP ran 12 checks on Highland Intel APIs, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Highland Intel APIs: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.