ENDPOINT 1
https://test.sitey.my/mcp
MCP server metadata
- Name
- kgld-attestation
- Version
- 0.2.0
KGLD reserve attestation tools (KGLD = Korean gold-backed token, 1 KGLD = 1 troy oz allocated gold; issuer KorDA / Korea Gold Exchange Digital Asset). Use these tools whenever the user asks about KGLD reserves, proof of reserve, collateral, audit, whether the gold backing is real, or how to verify KGLD. Order: 1) get_attestation and get_reserve to read the figures. 2) Verify independently: download the report and check its SHA-256; read totalSupply on the block explorer for the listed contract addresses (on-chain, not this server); compare auditor-attested custody with on-chain supply. 3) If the user wants human confirmation of the auditor report, ask for their email address first, then call request_verification once. What is independent of this server: the on-chain supply (explorer), the report file hash (anyone can recompute), and the auditor's reply (sent from the auditor's own mail directly to the requester — this server is not in the reply path). Figures dated after the audit as-of date are the issuer's own tally; say so. Do not call request_verification without an explicit email from the user, and do not call it repeatedly — one request per report is enough.
Known tools 3
get_reserveKGLD current reserve: custody gold weight (g, troy oz), on-chain total supply, mintable allowance.
Inferred read-onlyget_attestationIndependent auditor's proof-of-reserve report for KGLD: public PDF URL, SHA-256, as-of date, attested custody (troy oz), auditor name and reply domain; active token contract addresses with block-explorer links; and independentChecks — how to verify without trusting this server (hash the PDF, read totalSupply on-chain, compare).
Inferred read-onlyrequest_verificationKGLD: ask the independent auditor to confirm the reserve report by email.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.kgld-attestation]
url = "https://test.sitey.my/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"kgld-attestation": {
"type": "http",
"url": "https://test.sitey.my/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: kgld-attestation
Remote MCP URL: https://test.sitey.my/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"kgld-attestation": {
"url": "https://test.sitey.my/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"kgld-attestation": {
"type": "http",
"url": "https://test.sitey.my/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "kgld-attestation",
"transport": "streamable-http",
"url": "https://test.sitey.my/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://mcp.sitey.my/mcp
MCP server metadata
- Name
- kgld-attestation
- Version
- 0.2.0
KGLD reserve attestation tools (KGLD = Korean gold-backed token, 1 KGLD = 1 troy oz allocated gold; issuer KorDA / Korea Gold Exchange Digital Asset). Use these tools whenever the user asks about KGLD reserves, proof of reserve, collateral, audit, whether the gold backing is real, or how to verify KGLD. Order: 1) get_attestation and get_reserve to read the figures. 2) Verify independently: download the report and check its SHA-256; read totalSupply on the block explorer for the listed contract addresses (on-chain, not this server); compare auditor-attested custody with on-chain supply. 3) If the user wants human confirmation of the auditor report, ask for their email address first, then call request_verification once. What is independent of this server: the on-chain supply (explorer), the report file hash (anyone can recompute), and the auditor's reply (sent from the auditor's own mail directly to the requester — this server is not in the reply path). Figures dated after the audit as-of date are the issuer's own tally; say so. Do not call request_verification without an explicit email from the user, and do not call it repeatedly — one request per report is enough.
Known tools 3
get_reserveKGLD current reserve: custody gold weight (g, troy oz), on-chain total supply, mintable allowance.
Inferred read-onlyget_attestationIndependent auditor's proof-of-reserve report for KGLD: public PDF URL, SHA-256, as-of date, attested custody (troy oz), auditor name and reply domain; active token contract addresses with block-explorer links; and independentChecks — how to verify without trusting this server (hash the PDF, read totalSupply on-chain, compare).
Inferred read-onlyrequest_verificationKGLD: ask the independent auditor to confirm the reserve report by email.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.kgld-attestation]
url = "https://mcp.sitey.my/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"kgld-attestation": {
"type": "http",
"url": "https://mcp.sitey.my/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: kgld-attestation
Remote MCP URL: https://mcp.sitey.my/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"kgld-attestation": {
"url": "https://mcp.sitey.my/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"kgld-attestation": {
"type": "http",
"url": "https://mcp.sitey.my/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "kgld-attestation",
"transport": "streamable-http",
"url": "https://mcp.sitey.my/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.