Documentation

    Amazon Web Services

    Microsoft Azure

    RapidAPI

Last Update: 2026-10-09

MCP Server


Table of Content


Subscribe on AWS Marketplace
Connect your AgentCore Gateway
Available tools
Protocol reference
Code samples
Billing and free trial
API Usage Dashboard & API Key Retrieval
Troubleshooting

The MCP Server is a single Model Context Protocol endpoint that exposes every SilverLining.Cloud API your AWS account is entitled to use. You register one URL as a target on your Amazon Bedrock AgentCore Gateway, and your agent discovers the tools itself and calls them by name. There is no client library to install and no integration code to write.

One subscription covers all eighteen tools. If you already subscribe to individual SilverLining.Cloud APIs, those keep billing exactly as they do today — see Billing and free trial below.

Subscribe on AWS Marketplace


Navigate to the SilverLining.Cloud MCP Server listing on the AWS Marketplace and select the "View purchase options" button to proceed.

On the following page, click the "Subscribe" button to initiate the subscription process.

After subscribing, you will need to set up your account on our platform. Do this by clicking the "Set up your account" button twice.

You will be directed to the registration page. Here, fill in your account details in the provided fields. Once you have entered all necessary information, click the 'Subscribe' button to proceed.

Upon successful registration, your unique API key will be displayed. It is crucial to store this key in a secure location for future use. This is the key your AgentCore Gateway will present to the MCP Server as outbound authentication.

Connect your AgentCore Gateway


In the Amazon Bedrock console, open AgentCore and create a Gateway, or open the one your agent already uses. Then add a target of type MCP server with the following settings:

Target type:      MCP server
Endpoint URL:     https://mcp.api.silverlining.cloud/mcp
Outbound auth:    API key
Header name:      x-api-key
Header value:     <YourApiKey>

That is the whole integration. The Gateway calls tools/list with your key, so the tool list it caches is already scoped to your subscription — your agent is never shown a tool it cannot call.

Because the list is cached per target, re-synchronise the target whenever your subscriptions change. If you subscribe to a new API and the matching tools do not appear, that refresh is almost always the reason.

A Gateway allows ten targets by default and up to 200 tools per target, so one SilverLining.Cloud target costs you a single slot rather than one per API.

The endpoint also works with any other MCP client that can send an HTTP header. It is a standard streamable HTTP MCP server; nothing about it is specific to AgentCore.

Available tools


Eighteen tools across seven APIs. Each tool carries its own description and JSON schema, so your agent decides when to use it without any prompting from you.

Documents and OCR

  • silverlining_extract_document_text — read text out of a PDF or image, optionally only a page range
  • silverlining_get_ocr_result — collect the result of a long-running OCR job (never billed)

Short links

  • silverlining_shorten_url — create a short link, with optional custom slug, domain and expiry
  • silverlining_update_short_link — retarget an existing link without issuing a new one
  • silverlining_get_link_clicks — click statistics for a slug

Currency

  • silverlining_get_exchange_rates — every rate for one base currency
  • silverlining_convert_currency — convert an amount between two currencies
  • silverlining_get_historical_rate — one pair on one past date

Screenshots

  • silverlining_capture_screenshot — full page or element, mobile or desktop, optionally through a country proxy

QR codes

  • silverlining_create_qr_code — a static code with colours, logo and error correction
  • silverlining_create_dynamic_qr_code — a code whose destination you can change later
  • silverlining_update_dynamic_qr_code — repoint a dynamic code that is already printed
  • silverlining_get_qr_scans — scan statistics for a dynamic code

Validation

  • silverlining_validate_email — deliverability, disposable and role-account checks
  • silverlining_validate_phone — line type, carrier and formatting

Internet intelligence

  • silverlining_locate_ip — geolocation for an IP address
  • silverlining_dns_lookup — A, MX, NS, TXT, SOA and more for a domain
  • silverlining_whois_lookup — registration and ownership for a domain
Protocol reference


You do not normally call this endpoint by hand — your MCP client does. It is documented here so you can test the connection and debug it.

URL endpoint: https://mcp.api.silverlining.cloud/mcp


Method: POST  (JSON-RPC 2.0)


"header": {
  "x-api-key": STRING,
  "Content-Type": "application/json"
}


Supported methods

  • initialize — negotiates the protocol version and returns server capabilities
  • tools/list — the tools this API key is entitled to, with full JSON schemas
  • tools/call — runs one tool and returns its result
  • ping — liveness check

Protocol versions

2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26 are supported. Send your preferred version in initialize and the server replies with the one it will use.

Request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "silverlining_dns_lookup",
    "arguments": { "domain": "example.com" }
  }
}


Response:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [{ "type": "text", "text": "{ ... }" }],
    "isError": false
  }
}


Tool results come back as a JSON document inside a text content block, which is what MCP clients expect. A failure sets isError to true and puts a readable explanation in the same place, rather than returning a JSON-RPC error — so your agent can read the problem and decide what to do instead of the call simply breaking.

Requests are answered within 29 seconds. Long OCR jobs are therefore submitted and collected in two steps, using silverlining_extract_document_text and then silverlining_get_ocr_result.

Code Samples


The samples below list the tools your key can reach, then run a DNS lookup. Use them to confirm your key works before you point a Gateway at the endpoint.

# List the tools this key is entitled to
curl --location 'https://mcp.api.silverlining.cloud/mcp' \
--header 'x-api-key: <YourApiKey>' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
}'

# Call one of them
curl --location 'https://mcp.api.silverlining.cloud/mcp' \
--header 'x-api-key: <YourApiKey>' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
        "name": "silverlining_dns_lookup",
        "arguments": { "domain": "example.com" }
    }
}'
Billing and free trial


Usage is billed per request through your AWS Marketplace subscription, at the same price as the standalone API. There is no monthly fee and no minimum.

OCR, per page processed                    $0.002
Website screenshot                        $0.005
Short link API request                    $0.004
Static QR code                            $0.001
Dynamic QR code                           $0.010
Email or phone validation                 $0.002
IP, DNS or Whois lookup                   $0.001
Exchange rate request                     $0.002


Your first 100 calls in every one of those categories are free, so you can wire up an agent and watch it work before anything is charged.

Three details worth knowing:

  • OCR is billed per page, not per document. Passing page_from and page_to is the single biggest lever on cost for a long PDF.
  • A screenshot requested through a country proxy costs three times the standard rate, because the upstream request does.
  • Collecting an OCR result with silverlining_get_ocr_result is free, as are redirects, link clicks and QR scans. You are billed when you ask us to do work, not when someone uses what we made.

If you already subscribe to an individual API

Nothing changes. A tool belonging to an API you subscribe to directly is billed by that subscription, on the terms you already have, and the MCP Server adds nothing on top. Holding both can never bill you twice.

You can also use the MCP Server with no MCP subscription at all. In that case tools/list returns only the tools of the APIs you already bought — a free way to give your agents the APIs you are paying for today.

API Usage Dashboard


You can monitor and review your API activity in the API Usage Dashboard at https://silverlining.cloud/dashboard. Simply log in with your email address, then verify access using the one-time password (OTP) sent to your inbox. The dashboard displays your latest 1,000 API requests directly in the browser for quick inspection. For full analytics, you can also download the complete request history as a CSV file. After clicking the download button, a secure download link will be sent to your email address.

Calls made through the MCP Server appear alongside your direct API requests, prefixed with mcp: and the tool name, so you can see at a glance which traffic came from an agent.

If you need to change your account email address, contact our support team.


API Key Retrieval


If you've lost your API key, log in to the web dashboard (see above) and open the Settings tab. There, you'll find all API keys for all services you're subscribed to.

Troubleshooting

"message": "Forbidden"

The request reached the endpoint without a valid API key. Check that the x-api-key header is present and that the value is the key issued when you registered. If your Gateway target is configured for a different outbound auth type, this is what you will see.

tools/list comes back empty, or is missing tools I expect

The tool list is scoped to what your AWS account is entitled to, so an empty list means no active subscription was found for the key you presented. If tools are missing rather than absent entirely, you are most likely looking at a cached list: AgentCore Gateway caches tools/list per target, so re-synchronise the target after any subscription change.

"This account has no active subscription covering …"

Entitlement is checked again when a tool is called, not only when the list is built — so a subscription that lapsed after the list was cached produces this message. Subscribe to the MCP Server for every tool, or to the individual API on its own, then re-synchronise your target.

"Rate limit reached for this subscription"

Requests are throttled per subscription. Agents often fan out several tool calls at once, which is the usual cause. Retry after a short pause, or stagger the calls. If you need a higher limit, contact our support team.

A call timed out

The endpoint answers within 29 seconds. For OCR on a large document, submit the job with silverlining_extract_document_text and collect it with silverlining_get_ocr_result instead of waiting on a single call — collection is never billed. Narrowing a screenshot to one element, or an OCR job to a page range, also brings a slow call back inside the window.

How can I see my API usage and associated costs?

Navigate to our API Usage Dashboard to view past API requests. There, you can download a CSV export of all requests made.

To check the associated costs of your API usage, use the AWS Billing dashboard:

  1. Navigate to AWS Cost Management.
  2. In the left panel, select Cost Explorer.
  3. Use the cost filters on the right side. Under Legal entity, filter for SilverLining.Cloud.

How can I cancel my subscription?

To cancel your subscription, follow these steps:

  1. Go to the AWS Marketplace Console at https://aws.amazon.com/marketplace/library. Ensure that you are logged into the account that is subscribed to the product you want to cancel.
  2. Find the product you want to cancel and click on 'Manage.'
  3. Click on 'Actions' and then select 'Cancel subscription.'

For more detailed instructions, visit the AWS Marketplace Buyer Guide at https://docs.aws.amazon.com/marketplace/latest/buyerguide/cancel-subscription.html.