Agam
REMOTE · HOME.ASHWINGOPALSAMY.IN
Keyless public journal reads: construction costs, day-wise work, source precision and exact INR.
Available components
Last scanned (12 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Documents and Files
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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 305 tokens (~76/item across 4 items; 2 tools + 2 resources), lean.Pass
- 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- 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 4 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.
- 23 Oct 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.
- 21 Oct 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.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 15 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.
- 12 Oct 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.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 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.
- 6 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
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 23 Oct 2026 · Probed https://home.ashwingopalsamy.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ashwingopalsamy.in | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4af618e49b4fded80e1f8c26a3413aed |
| SANs: ashwingopalsamy.in, home.ashwingopalsamy.in, *.home.ashwingopalsamy.in | ||||||
| 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 home.ashwingopalsamy.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| ashwingopalsamy.in. | present | 2371 | 13 | Verified |
| home.ashwingopalsamy.in. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://home.ashwingopalsamy.in/mcp | Verified | 200 | |
| http (plaintext) | http://home.ashwingopalsamy.in/mcp | HTTPS enforced | 301 | https://home.ashwingopalsamy.in/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_content Read a public journal record ~58
Retrieve a stable ID returned by search, including exact INR/paise values, precision, source and freshness. Read-only; private evidence and arbitrary paths are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable published content ID; never a path or URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical | string | yes | – |
| cost | object | – | – |
| description | string | yes | – |
| id | string | yes | Stable published content ID; never a path or URL. |
| kind | string | yes | – |
| language | string | yes | – |
| last_updated | string | yes | – |
| review | – | yes | – |
| revision | string | yes | – |
| source | array | yes | – |
| summary | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| visibility | string | yes | – |
| work | object | – | – |
No examples provided.
search_content Search journal records ~111
Search literal words in public normalized journal records. Use before reading a returned ID. No private results, generated answers or external fetches. Cursor expires after one hour; maximum 100 records.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque next_cursor from the preceding page; expires after one hour. |
| kind | string | – | – |
| limit | integer | – | Page size; default 20, maximum 100. |
| q | string | yes | Literal words in public titles and normalized descriptions; no regex or generated answers. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| limit | integer | yes | – |
| next_cursor | string|null | yes | – |
| snapshot | string | yes | – |
No examples provided.
How do I install the Agam MCP server?
Agam is a hosted endpoint at https://home.ashwingopalsamy.in/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 · home.ashwingopalsamy.in
claude mcp add --transport http in-ashwingopalsamy-home-agam-journal 'https://home.ashwingopalsamy.in/mcp'
What is the Agam MCP server?
Agam is an MCP server listed in the public MCP registry as in.ashwingopalsamy.home/agam-journal. Keyless public journal reads: construction costs, day-wise work, source precision and exact INR. This page covers its hosted endpoint (https://home.ashwingopalsamy.in/mcp).
Is the Agam MCP server safe to use?
Agam scores 85 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 Agam MCP server expose?
Agam exposes 2 tools: search_content, get_content. Their descriptions and schemas cost roughly 169 tokens of context every time the server is loaded.
Does the Agam MCP server require authentication?
No. We connected to Agam without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agam MCP server still maintained?
Agam is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.