Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Application Migration Service

MCP server · mgn.us-east-1.amazonaws.com · found in a public registry · checked since 2026-10-20

Live, key asked · latest check

As JSON

GET https://mgn.us-east-1.amazonaws.com

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest137 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-20under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-10-2010——————
7 dayssince 2026-10-2010——————
30 dayssince 2026-10-2010——————

Milliseconds, from eastern North America, timing a passing answer. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Access

Our latest check
Asked for credentials
Stated
Credentials needed, by its OpenAPI description (API key)
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-20. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/5): ✗ what it does is unclear to our placement; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA
Live, key asked HTTP 403 137 ms

What these figures do not show

  • A passing check means the API's server answered one plain request from us, with no key and no redirects followed (web-reach/1): a response a live API gives without credentials (2xx, a redirect, 400, 401, 403, 405, 406, 415, 422 or 429). It does not show that its operations work, what they cost, or what a key gives access to.
  • Listed in APIs.guru, a collection of OpenAPI descriptions; the address, the categories and the security schemes come from its description of the API, as stated there. The description itself is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_2682b392d6098cca