Friction
REMOTE · FRICTION.GRAIN64.COM
Sourced pain points, feature requests, workarounds and switching reasons of B2B software users.
Available components
Last scanned (23 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 403 tokens (~134/item across 3 items; 3 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 80
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://friction.grain64.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=friction.grain64.com | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e1f5e64d69889fe20e590fd6cb04f768 |
| SANs: friction.grain64.com | ||||||
| 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 friction.grain64.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| grain64.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://friction.grain64.com/mcp | Verified | 200 | |
| http (plaintext) | http://friction.grain64.com/mcp | HTTPS enforced | 301 | https://friction.grain64.com/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 →
get_product_summary Get a product summary ~79
What users of one product struggle with: counts, the main problem areas, and the free-preview reports per category (pain points, feature requests, workarounds, switching reasons) with their source links, plus the page and pricing links for the full list.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product slug, name or domain, for example grafana. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | object | yes | – |
| counts | object | yes | – |
| note | string | – | – |
| product | object | yes | – |
| top_areas | array | yes | – |
No examples provided.
list_products List products ~108
List the software products that have a page on Friction, most-documented first, with counts of reports, recurring themes and sources. Optionally filter by category slug and by a name or domain fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, for example analytics. |
| limit | integer | – | How many products to return (default 50). |
| offset | integer | – | How many products to skip (default 0). |
| q | string | – | Part of a product name or domain. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| offset | integer | yes | – |
| products | array | yes | – |
| returned | integer | yes | – |
| total | integer | yes | – |
No examples provided.
search_items Search feedback reports ~101
Search the free-preview feedback reports of one product, optionally by category and by words in the title or summary (all words must match). Each report carries the source threads (URL, date, quoted excerpt, state) behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | pain, request, workaround or switching. |
| product | string | yes | Product slug, name or domain, for example grafana. |
| q | string | – | Words to find in the title or summary. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
| note | string | – | – |
| product | object | yes | – |
| query | object | yes | – |
No examples provided.
How do I install the Friction MCP server?
Friction is a hosted endpoint at https://friction.grain64.com/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 · friction.grain64.com
claude mcp add --transport http com-grain64-friction 'https://friction.grain64.com/mcp'
What is the Friction MCP server?
Friction is an MCP server listed in the public MCP registry as com.grain64/friction. Sourced pain points, feature requests, workarounds and switching reasons of B2B software users. This page covers its hosted endpoint (https://friction.grain64.com/mcp).
Is the Friction MCP server safe to use?
Friction scores 84 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 Friction MCP server expose?
Friction exposes 3 tools: list_products, get_product_summary, search_items. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Does the Friction MCP server require authentication?
No. We connected to Friction without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Friction MCP server still maintained?
Friction 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 Friction MCP server?
VerifyMCP ran 13 checks on Friction, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.