com.honesthook/social-data
REMOTE · HONESTHOOK.COM
Instagram, TikTok, Threads, Bluesky and 8 more: one API, one key, one JSON shape
Available components
Last scanned (13 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category News and Social
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
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 yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “archive_coverage” rewrote its description, which is the text the model reads security
- Tool “check_balance” rewrote its description, which is the text the model reads security
- Tool “fetch_posts” rewrote its description, which is the text the model reads security
- Tool “fetch_profile” rewrote its description, which is the text the model reads security
- Tool “get_docs” rewrote its description, which is the text the model reads security
- Tool “list_endpoints” rewrote its description, which is the text the model reads security
- Tool “list_platforms” rewrote its description, which is the text the model reads security
- Tool “pricing” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “archive_movers” functional
- New tool “archive_trends” functional
- New tool “github_repos” functional
- New tool “profile_history” functional
- “fetch_posts” reworded the description of “limit” cosmetic
- Tool “archive_coverage” changed its title: Archive coverage by niche cosmetic
- Tool “check_balance” changed its title: Check credit balance cosmetic
- Tool “fetch_posts” changed its title: Fetch recent posts cosmetic
- Tool “fetch_profile” changed its title: Fetch a public profile cosmetic
- Tool “get_docs” changed its title: API docs in one page cosmetic
- Tool “list_endpoints” changed its title: List API endpoints cosmetic
- Tool “list_platforms” changed its title: List supported platforms cosmetic
- Tool “pricing” changed its title: Pricing and free allowance cosmetic
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
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 21 Nov 2026 · Probed https://honesthook.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=honesthook.com | CN=YR1,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 5ffebeffae84fae6f8a27946c14fd970024 |
| SANs: honesthook.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of honesthook.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| honesthook.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://honesthook.com/api/mcp | HTTP error | 402 | |
| http (plaintext) | http://honesthook.com/api/mcp | HTTPS enforced | 308 | https://honesthook.com/api/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 →
archive_coverage Archive coverage by niche ~71
How much trend history HonestHook already holds, by niche — AI agents, developer tools, indie SaaS — with the most recent hourly window captured. Use this to check whether the archive goes back far enough for your question before you build on it. No API key needed, and it costs 0 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
archive_movers Biggest movers in a niche ~250
Who grew and who shrank most in a niche, over a window we have already archived — the comparison done for you, ranked. Call `archive_coverage` first: it lists the valid niche ids and how far back each one goes. `hours` is 1 to 720 (30 days) and defaults to 24; `limit` is 1 to 100 and defaults to 20. A value outside the range is rejected rather than silently trimmed. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 10 credits — free when nothing moved.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | How many hours back the window goes. Optional, 1 to 720, 24 by default. Outside that range the API answers 400. |
| limit | integer | – | How many movers to return. Optional, 1 to 100, 20 by default. Outside that range the API answers 400. |
| niche | string | yes | The niche id, as `archive_coverage` returns it — for example `ai-agents`. A niche we do not archive is refused by the API. |
No output schema declared.
No examples provided.
archive_trends Niche trend history ~266
How a niche moved over a window we have already archived, grouped by item: where each account stood then and where it stands now. This is the question nobody can answer after the fact — nobody photographs the past retroactively. Call `archive_coverage` first for the valid niche ids and how far back the archive goes. `from` and `to` are ISO 8601; without them you get the last 7 days, and the archive caps any window at 90 days. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 1 credit — charged even when the result is empty.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start of the window, ISO 8601 (`2026-09-05T00:00:00Z`). Optional. Anything else answers 400 rather than being guessed at. |
| limit | integer | – | How many items to return. Optional. |
| niche | string | yes | The niche id, as `archive_coverage` returns it — for example `ai-agents`. A niche we do not archive is refused by the API. |
| to | string | – | End of the window, ISO 8601. Optional, defaults to now. |
No output schema declared.
No examples provided.
check_balance Check credit balance ~88
How many credits are left on your HonestHook API key: the free monthly allowance, the purchased balance, when the allowance renews, and what this cycle spent, broken down by endpoint. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key. Checking the balance costs 0 credits — reading it never changes it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fetch_posts Fetch recent posts ~358
Read the recent posts of one public profile: the text, likes, replies, reposts, quotes, the post URL and when it was published. Threads, Bluesky, Mastodon and Telegram. Boosts and reposts of other people are filtered out — you get what the account itself wrote, its replies included. `limit` is optional on Bluesky and Mastodon, and each has its own range: a value outside it is rejected rather than silently trimmed. Threads does not accept `limit` at all and answers 400 if you send it — its posts arrive inside the same document as the profile, so there is no upstream to ask for a count. Telegram ignores `limit`: it returns every post in the public preview page, with no login and no bot token. Telegram's `followers` is always null on this endpoint — the preview page only prints the subscriber count abbreviated, not exact. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The account handle, without the leading @. On Mastodon it must be `user@instance`, because the same local name exists on many servers. |
| limit | integer | – | How many posts to return. Optional, and Bluesky and Mastodon only. The valid range depends on the platform and the API rejects a value outside it instead of trimming it, so the count you get is never… |
| platform | string | yes | Which platform to read the posts from. |
No output schema declared.
No examples provided.
fetch_profile Fetch a public profile ~165
Read one public profile and get the numbers back: follower count, following count, posts count, bio, verified flag and avatar. Works on Instagram, TikTok, Threads, Bluesky, Mastodon, GitHub, Pinterest, SoundCloud, Linktree, Medium and Telegram. Mastodon handles are always `user@instance` — the local name alone identifies nobody. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The account handle, without the leading @. On Mastodon it must be `user@instance`, because the same local name exists on many servers. |
| platform | string | yes | Which platform to read the profile from. |
No output schema declared.
No examples provided.
get_docs API docs in one page ~66
How to authenticate, how the response envelope is shaped, what happens when credits run out, and where to get a free key with 1,000 credits a month and no card. Read this before writing code against the API. No API key needed, and it costs 0 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
github_repos List a GitHub account's repos ~167
The public repositories of one GitHub account, with stars and forks. GitHub only — this is the one platform whose repositories we read. `limit` is optional: 30 by default, which is GitHub's own page size, and 100 at most, which is GitHub's ceiling. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The GitHub username, without the leading @: letters, digits and single hyphens, up to 39 characters. |
| limit | integer | – | How many repositories to return. Optional, 30 by default, 100 at most. Outside that range the API answers 400. |
No output schema declared.
No examples provided.
list_endpoints List API endpoints ~98
List every HonestHook API endpoint: public profiles (followers, following, posts count, bio, verified), recent posts, the historical trend archive, and per-profile history. Returns the URL and the query parameters for each, and says which ones you can call as a tool on this server — profiles through `fetch_profile`, posts through `fetch_posts` — and which are HTTP only. No API key needed, and it costs 0 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_platforms List supported platforms ~100
List every social platform HonestHook can read right now — the platforms you'd otherwise write a scraper for: Instagram, TikTok, Threads, Bluesky, Mastodon, GitHub, Pinterest, SoundCloud, Linktree, Medium, Telegram — and what a handle looks like on each one. Use this before asking for a profile, to check the platform is covered and the handle format is right. No API key needed, and it costs 0 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pricing Pricing and free allowance ~70
What each HonestHook call costs in credits, and which calls are free when they find nothing. Includes the free monthly allowance that every key gets with no card, at https://honesthook.com/docs#key. Use this to estimate cost before building. No API key needed, and it costs 0 credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
profile_history Daily history of a profile ~240
The daily history of one public profile we have already archived: how its follower count moved, day by day. ⚠️ It only covers what was captured after somebody first asked for that profile — the series starts the day of the first call and never earlier, and the response says so in `covered_from`. A handle nobody ever asked for comes back with an empty series, which means 'we never looked', never 'nothing changed'. Requires an API key sent as `Authorization: Bearer <key>` — free key at https://honesthook.com/docs#key; costs 1 credit — free when nothing is found.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start of the window, ISO 8601. Optional. Anything else answers 400. |
| handle | string | yes | The account handle, without the leading @. On Mastodon it must be `user@instance`, because the same local name exists on many servers. |
| limit | integer | – | How many days to return. Optional. |
| platform | string | yes | Which platform the archived profile is on. |
| to | string | – | End of the window, ISO 8601. Optional. |
No output schema declared.
No examples provided.
How do I install the com.honesthook/social-data MCP server?
com.honesthook/social-data is a hosted endpoint at https://honesthook.com/api/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 · honesthook.com
claude mcp add --transport http com-honesthook-social-data 'https://honesthook.com/api/mcp'
What is the com.honesthook/social-data MCP server?
com.honesthook/social-data is an MCP server listed in the public MCP registry as com.honesthook/social-data. Instagram, TikTok, Threads, Bluesky and 8 more: one API, one key, one JSON shape. This page covers its hosted endpoint (https://honesthook.com/api/mcp).
Is the com.honesthook/social-data MCP server safe to use?
com.honesthook/social-data scores 25 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 com.honesthook/social-data MCP server expose?
com.honesthook/social-data exposes 12 tools: list_platforms, list_endpoints, pricing, archive_coverage, get_docs, and 7 more. Their descriptions and schemas cost roughly 1,939 tokens of context every time the server is loaded.
Does the com.honesthook/social-data MCP server require authentication?
Its publisher declares no required credentials for com.honesthook/social-data. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the com.honesthook/social-data MCP server still maintained?
com.honesthook/social-data is still listed as active in the MCP registry. We last reached this channel on 21 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 com.honesthook/social-data MCP server?
VerifyMCP ran 5 checks on com.honesthook/social-data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about com.honesthook/social-data: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.