mcp-my-site
REMOTE · AI.POURNASSERIAN.COM · 2 COMPONENTS
Search and fetch tools for one website, served from an index you build with the mcpmysite crawler.
Available components
Last scanned (4 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 764 tokens (~382/item across 2 items; 2 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 Management63
- Stability observed for 19 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Server version: 0.3.0 → 0.4.0 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
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://ai.pournasserian.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pournasserian.com | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6dea0c3c5fd9dd99134d71aec1c4e67f |
| SANs: pournasserian.com, *.pournasserian.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 secure
Validation of ai.pournasserian.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pournasserian.com. | present | 2371 | 13 | Verified |
| ai.pournasserian.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| 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://ai.pournasserian.com/mcp | Verified | 200 | |
| http (plaintext) | http://ai.pournasserian.com/mcp | HTTPS enforced | 301 | https://ai.pournasserian.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 →
fetch Fetch a page ~82
Returns the full content of one page of the website as Markdown in text, with its title, description, language and last modified date. Pass the id (or url) of a search result.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string|null | – | The id of a search result. |
| url | string|null | – | Absolute URL of the page. An alternative to id; pass either one. |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | yes | – |
| id | string | yes | – |
| language | string | yes | – |
| modified | string|null | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
search Search the site ~192
Searches the website Amir Pournasserian (https://pournasserian.com/): Serial entrepreneur and hands-on AI architect. I build AI and platform systems that have to keep working once they meet production, compliance and scale. Hybrid keyword and semantic search over its 82 pages, indexed on 2026-10-31; returns the best matching pages with a short snippet each. When hasMore is true, call again with offset set to the previous offset plus limit to see further results. Call fetch with a result's id or URL to read the whole page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of pages to return, 1 to 20. Default 10. |
| offset | integer | – | Pages to skip before the first result, for paging. Default 0; values past the server's cap are clamped. |
| query | string | yes | What to look for. Natural language or keywords. |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| indexedAt | string | yes | – |
| keywordOnly | boolean | yes | – |
| query | string | yes | – |
| results | array | yes | – |
| total | integer | yes | – |
No examples provided.
How do I install the mcp-my-site server?
mcp-my-site is a hosted endpoint at https://ai.pournasserian.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 · ai.pournasserian.com
claude mcp add --transport http pournasserian-mcp-my-site 'https://ai.pournasserian.com/mcp'
What is the mcp-my-site server?
mcp-my-site is listed in the public MCP registry as io.github.pournasserian/mcp-my-site. Search and fetch tools for one website, served from an index you build with the mcpmysite crawler. This page covers its hosted endpoint (https://ai.pournasserian.com/mcp).
Is the mcp-my-site server safe to use?
mcp-my-site scores 79 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 mcp-my-site server expose?
mcp-my-site exposes 2 tools: search, fetch. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.
Does the mcp-my-site server require authentication?
No. We connected to mcp-my-site without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mcp-my-site server still maintained?
mcp-my-site 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.