Latent Mile: Local 35mm colour developing and scans

com.forevenza.servicesPublished by services.forevenza.comv1.0.0Updated Nov 7, 2026

Local 35mm C-41 developing & scans: batch advice and local availability requests

The publisher's own server: Requirements Desk

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Connects an assistant to Latent Mile, a local 35mm C-41 developing and scanning service, to describe a film batch, submit a request, and review and accept…

What you can do
  • Learn what the service does and which request fields it expects
  • Submit a film batch requirement and get a reference number for it
  • Resume a recorded request and read any linked offers using receipt credentials
  • Inspect an offer's exact terms, terms hash, order state and payment links
  • Accept or decline an offer on inspected terms
  • Record a payment release approval where the inspected order allows it
When to use it
Useful when someone wants an assistant to prepare and submit a 35mm C-41 developing and scan request to a local lab, then track the request and compare, accept or decline the resulting offers without retyping details.
Requirements
Remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared. Requests are progressed by email, so an email address is needed to receive replies, and receipt or offer link credentials are needed to resume a request or inspect an offer.
Before you install
Submitting a request records data with the provider and is not an order or confirmed drop-off. Accepting an offer places an order and requires the exact terms hash plus explicit acceptance; release_payment records approval and does not itself pay the processor, so payment happens through the processor links. Contact details are kept apart from the request, and requests and offers are reachable only with the receipt or offer credentials, which should be kept safe.

Installation

In SourceWeft

  1. Open Latent Mile: Local 35mm colour developing and scans in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.forevenza.services%2Flatentmile/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "latent-mile-local-35mm-colour-developing": {
      "type": "http",
      "url": "https://latentmile.forevenza.com/mcp"
    }
  }
}

Tools

7

describe_business

About Latent Mile

What Latent Mile does, what happens to a request, and the request fields.

Takes no parameters.

submit_request

Send a requirement

Send a requirement to Latent Mile. It is kept with a reference number. Your request is recorded with a reference number. Latent Mile checks local handoff options, scan scope, deadline feasibility, price, handling and negative-return arrangements and replies by email when an address is left. Nothing is ordered or committed until you agree terms. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.

Parametersneedrequiredactionbudgettimingcontactquantitygeographycontinuationspecificationsrequested_fields

request_status

request status

Resume a requirement using the receipt credentials. Read the recorded requirement and any linked offers. Contact details are kept apart.

Parametersidrequiredtokenrequired

inspect_offer

inspect offer

Read the exact authorized terms, terms hash, order state and processor payment links. Use the offer link credentials, or credentials of the request explicitly linked to this offer.

Parametersidrequiredtokenrequired

accept_offer

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.

Parametersidrequirednamerequiredtokenrequiredacceptrequiredorganizationterms_sha256requiredpurchase_order

decline_offer

decline offer

Decline an issued offer on its inspected terms.

Parametersidrequiredtokenrequiredreasonterms_sha256required

release_payment

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.

Parametersidrequirednametokenrequiredconfirmrequiredpaymentrequiredterms_sha256required

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Forevenza integrations