Linklamp: Switch swap or repatch visit in Dearborn, MI, under your remote engineer
com.forevenza.services/linklamp · v1.0.0 · MCP 2025-11-25
Dearborn MI switch swap and repatch visits for MSPs; remote signoff; proposal by email
Reachability
reachable
checked 2026-11-21 05:43 UTC
Registry status active
Tools pinned 23
c3277b6d7433
Tools last changed
2026-11-15
Provenance
Registry namespace com.forevenza.services
(domain verified by the official registry)
Remote endpoints
https://linklamp.meetinggrove.com/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-15 05:36 | tools changed | 0 added, 0 removed, 1 changed |
| 2026-11-10 05:31 | first capture | 23 tools pinned |
Pinned tool definitions (23)
| Tool | Description |
|---|---|
| describe_business | What Linklamp does (Switch swap or repatch visit in Dearborn, MI, under your remote engineer: Describe a Dearborn switch swap or repatch; Linklamp drafts the visit scope and emails a proposal with visit duties, exclusions, price and a... |
| submit_request | Send Linklamp a requirement (Switch swap or repatch visit in Dearborn, MI, under your remote engineer). The request is recorded with a reference at once. Linklamp reads the scope, open questions and any words kept as written, then... |
| check_availability | Times a provider has published, if any. With none, ask for an appointment with preferred windows. |
| request_appointment | Ask for an appointment at preferred windows (or hold a published time). It is a request until the provider confirms; the answer carries a status link. |
| interpret_requirement | Give Linklamp the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question,... |
| get_requirement | A Linklamp requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it. |
| edit_requirement | Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value. |
| send_requirement | Send the requirement to Linklamp once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the... |
| request_status | Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by... |
| inspect_offer | Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status... |
| accept_offer | Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state. |
| decline_offer | Decline an issued offer on its inspected terms. |
| release_payment | Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor. |
| retrieve_deliverable | Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or... |
| counter_offer | Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a... |
| submit_purchase_order | Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer... |
| state_purchasing_requirements | Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and... |
| report_vendor_status | Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business... |
| inspect_delivery | Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted... |
| answer_remedy | Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here... |
| appointment_status | Resume an appointment request: read provider-confirmed state, preferred windows and history. |
| cancel_appointment | Cancel this appointment request using its private credentials. |
| reschedule_appointment | Request new windows. An existing confirmed time stands until a provider confirms a replacement. |
Get alerted when this changes.
Email the moment com.forevenza.services/linklamp drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/com.forevenza.services/linklamp)
Maintain this server? Add the badge to your README. It links your users to this live status page.